159 results found

1. Sort by a specific array index

   When creating indexes and sorting with "normal" queries, it is possible to index/sort on a specific array index (e.g. foo.0.bar). I do this because the search results grid in our UI only has room to show the first foo.bar result, so it doesn't make sense visually to sort by additional objects which the user can't see.

   Since the new Atlas Search Sort syntax looks the same, I was hoping to do that with it as well, but it doesn't seem possible.

   Example:

   [
     { "xyzzy": "xyzzy",
       "foo": [ { "bar": "A" } ] },
   
     { "xyzzy": "xyzzy",
       "foo": [ { "bar": "B" }, { "bar": "D" } ] },
   
     { "xyzzy": "xyzzy",
       "foo": [ { "bar": "C" } ] }
   ]
   

   {
     index: "myindex",
     returnStoredSource: true,
     phrase: { path: "xyzzy", query: "xyzzy" },
     sort: { "foo.0.bar": -1 }
   }
   

   See: https://support.mongodb.com/case/01169701

   When creating indexes and sorting with "normal" queries, it is possible to index/sort on a specific array index (e.g. foo.0.bar). I do this because the search results grid in our UI only has room to show the first foo.bar result, so it doesn't make sense visually to sort by additional objects which the user can't see.

   Since the new Atlas Search Sort syntax looks the same, I was hoping to do that with it as well, but it doesn't seem possible.

   Example:

   [
     { "xyzzy": "xyzzy",
       "foo": [ { "bar": "A" } ] },
   
     { "xyzzy": "xyzzy",
       "foo": [

   … more
   3 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Data type coercion when document field type doesn't match index field type

   When a document field type doesn't match the index field type, it seems to be indexed as "blank" and won't match anything. Many data types are readily convertible between type representations. It would be great if Atlas Search could do that for us and would open up richer functionality by allowing us to use operators/analyzers/etc. on types that don't normally support them.

   My particular use case is to allow searching & sorting on numbers stored as strings. When creating indexes and sorting with "normal" queries, it is possible to sort numbers stored as strings by their numerical ordering rather than alphabetical by using { collation: { locale: "en_US", numericOrdering: true } } on the index definition and applying query.collation(Collation.of(Locale.US).numericOrdering(true)) to the query itself. I was hoping to do this with Atlas Search Sort as well, but it isn't possible.

   Examples:
   string "1000.00" = number 1000.00
   boolean true = number 1
   boolean true = string "true"
   etc.

   See: https://support.mongodb.com/case/01169737

   When a document field type doesn't match the index field type, it seems to be indexed as "blank" and won't match anything. Many data types are readily convertible between type representations. It would be great if Atlas Search could do that for us and would open up richer functionality by allowing us to use operators/analyzers/etc. on types that don't normally support them.

   My particular use case is to allow searching & sorting on numbers stored as strings. When creating indexes and sorting with "normal" queries, it is possible to sort numbers stored as strings by their numerical ordering rather than… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Token filter that removes duplicated entries

   Create a token filter or a tokenizer or even an option that removes duplicate words in fields  to avoid misleading scoring. 
   For example: if I insert a document with a property "Testing testing document", another with "Testing example" and a third with "Testing foo" and I search for "Testing foo", the first document receives a higher score.
   

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Allow comments in JSON code

   It would be great if we could keep comments in JSON generated items such as indexes (both MongoDB and Atlas Search)

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. knnBeta Limitations and Syntax

   I tested the new knnBeta operator today and it worked so far.
   Can we expect the current operator limitations to be gone by release?
   The current limitations make it virtually impossible to use the knn operator as a replacement for previous text operators (like text).
   I would prefer the filter parameter to be omitted and knn not have to be a top-level operator.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Allow indexing of only part of a collection

   Would be great to be able to create an Atlas Search index that only indexes part of a collection (like partialFilterExpression for a regular index). This would be valuable in situations where a collection is quite large (which would create a lot of unnecessary overhead) but only a small fraction of it needs to be searchable.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Mutli-select faceting / facets should not affect their own filter field

   I want to build multi-select facet without having to run separate queries to calculate bucket counts for each active filter. Described in detail here: https://yonik.com/multi-select-faceting/

   11 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   2 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. wildcard paths in index specifications

   It would make index specification easier in some cases if wildcards were possible in the paths. Yes we have dynamic indexing, but to keep the index size minimal and to be more flexible I want to index only the fields I really need. Consider the following example:

   Example document:

   {
   foo: {
   de: {
   field1: 'bar',
   field2: 'bar'
   },
   en: {
   field1: 'bar',
   field2: 'bar'
   },
   fr: {
   field1: 'bar',
   field2: 'bar'
   },
   }
   }

   Index specification:

   {
   "mappings": {
   "dynamic": false,
   "fields": {
   "foo": {
   "type": "document",
   "dynamic": false,
   "fields": {
   "$**": {
   "type": "document",
   "dynamic": false,
   "fields": {
   "field1": {
   "type": "string"
   }
   }
   }
   }
   }
   }
   }
   }

   This index would then index field1 in the object foo.*, where * stands for any field. So in this example foo.DE, foo.EN, foo.FR.

   This extension would help when you want to index nested objects where the field names of a layer are unknown or strongly dynamic, but dynamic: true would have too many unwanted side effects.

   It would make index specification easier in some cases if wildcards were possible in the paths. Yes we have dynamic indexing, but to keep the index size minimal and to be more flexible I want to index only the fields I really need. Consider the following example:

   Example document:

   {
   foo: {
   de: {
   field1: 'bar',
   field2: 'bar'
   },
   en: {
   field1: 'bar',
   field2: 'bar'
   },
   fr: {
   field1: 'bar',
   field2: 'bar'
   },
   }
   }

   Index specification:

   {
   "mappings": {
   "dynamic": false,
   "fields": {
   "foo": {
   "type": "document",
   "dynamic": false,
   "fields": {
   "$**": {
   "type": "document",
   "dynamic": false,
   "fields": {… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Ability to randomize score

   I would like to be able to add randomness to the search results' score.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Ability to return all documents in a collection

    I need to return all documents in a collection while boosting certain results which match my search criteria.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Ability to exclude documents matching a certain criteria from index

    We don't do physical deletion of documents, but a logical one, flagging them by setting a value for a deleted_at field.

    We would like an option to exclude documents where that field exists and is not null from the index, because they will never be returned and are only consuming space of the index.

    Currently we use a mustNot condition to exclude them, but of course they are still being indexed.

    The ideal would be to be able to define the exclusion criteria in the index definition.

    4 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Multiple Capture Groups in RegEx Tokenizer

    Currently the RegEx tokenizer only supports to either create a token from each match or for one capture group per match. This makes it impossible to reuse parts of the text for multiple tokens, for example when you want to tokenize "13.3" into "13" as well as "13.3" (our use case is searching products where we want to find a 13.3" device by searching for 13" as well as 13.3").

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Allow faceting on boolean fields

    Right now you can only facet on string, number, date fields.
    https://www.mongodb.com/docs/atlas/atlas-search/facet/#facet-definition

    I would like to also be able to facet on boolean fields.

    14 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminAmy (Admin, MongoDB) responded

    You can now transform documents for Atlas Search, enabling you to index and query Boolean fields as a String to support faceting. See how here.

14. Duplicate search index

    I want to be able to easily duplicate a search index in the Atlas UI.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Allow retrieval of individual score from embedded document search

    When using the emeddedDocuments operator to search you get a score per document, but not per embedded document. The aggregated score is either min/max/sum/mean but what I really need is the individual score from the embedded documents in order to further filter out the best matches.

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. search

    Allow scoring of individual embeddedDocument searches or allow $unwind phase before $search to enable fuzzy searching for specific embeddedDocument in array of embedded documents

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. add a setting to ignore the corpus term frequency for score calculation

    indexOption:docs omits per document frequencies, but it still uses the corpus frequency.

    it would be good to have a setting to ignore the corpus frequency as well

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Atlas full text search should support searching all field types

    Atlas full text search should support searching all fields types including text, dates, numbers and booleans.

    Atlas full text search at present supports searching in text values only. e.g. Searching for "2022" will not pick up documents that contain 2022 in the number fields.

    The functionality in it's current form does not have any way of searching for a given string value (which can be numeric, boolean or part of a date).

    3 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. .NET Driver

    It would be great if the .NET driver would support $search along with all the associated operators.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    2 comments  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Support for OR Conditions

    We need support for matching for one condition out of several. This is an important usecase for my requirements.

    e.g. $or: [{ "airlines": "United" }, { "ticket_price": { $lte: 600.00 } }]

    Thanks!

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating