149 results found

1. Automatically recreate Atlas Search indexes on a collection after the collection is dropped and recreated or overwritten

   Currently, if you use the $out aggregation stage to modify a collection with an Atlas Search index, you must delete and re-create the search index. Also, if another collection is renamed with dropTarget:true to an existing collection that already has Atlas Search indexes on it, then it is necessary to recreate the Atlas Search indexes after the collection rename completes (which involves dropping the original collection).

   This is a feature request to automatically recreate the pre-existing Atlas Search indexes on a collection after that collection is dropped and recreated (using either $out or renameCollection).

   8 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

2. Allow faceting on decimal fields

   I'd like to create a facet on a Price field stored as a decimal in my MongoDB documents. However, this doesn't give me the results I expect. I'm required to set the "boundaries" property on the facet to an array of integer or double values. However, when the facets are returned, they are all thrown into the "default" bucket.

   For example, if I were to declare the facet like this:

       facets: {
         price: {
           type: "number",
           path: "ProductPrice",
           // using plain integer boundaries 0,10,20,30 also fails
           boundaries: [ 0, 5.00, 10.00, 15.00, 20.00, 25.00, 30.00 ],
           default: "other",
         },
       },
   

   I incorrectly get results like this:

   "facet" : {
       "price" : {
           "buckets" : [
               {
                   "_id" : 0.0, 
                   "count" : NumberLong(0)
               }, 
               {
                   "_id" : 5.0, 
                   "count" : NumberLong(0)
               }, 
               {
                   "_id" : 10.0, 
                   "count" : NumberLong(0)
               }, 
               {
                   "_id" : 15.0, 
                   "count" : NumberLong(0)
               }, 
               {
                   "_id" : 20.0, 
                   "count" : NumberLong(0)
               }, 
               {
                   "_id" : 25.0, 
                   "count" : NumberLong(0)
               }, 
               {
                   "_id" : "other", 
                   "count" : NumberLong(1304)
               }
           ]
       }
   }
   

   Instead of having my results distributed across my price ranges.

   I'd like to create a facet on a Price field stored as a decimal in my MongoDB documents. However, this doesn't give me the results I expect. I'm required to set the "boundaries" property on the facet to an array of integer or double values. However, when the facets are returned, they are all thrown into the "default" bucket.

   For example, if I were to declare the facet like this:

       facets: {
         price: {
           type: "number",
           path: "ProductPrice",
           // using plain integer boundaries 0,10,20,30 also fails
           boundaries: [ 0, 5.00, 10.00, 15.00, 20.00, 25.00, 30.00 ],
           default: "other",
         },
       },
   

   … more

   7 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

3. Allow $match syntax in $search queries

   Currently, I am re-writing my queries that were previously using $match + $text queries using $search + compound. Firstly, this is a fair bit of work depending on the number of match clauses etc. Secondly, not all the operators that $match supports are supported inside $search/compound clauses causing product differences.

   Anything that would speed up migrating $match queries to use $search while maintaining query results would help take advantage of the $search capabilities without having to rework the entire query logic.

   As a side note, I'm aware that $match can follow a $search stage, but unfortunately this is really not performant as the $match stage is unable to use any of the native indices as confirmed by the documentation. There is another idea around allow $match to go before $search (which is great, I've upvoted). That could also help with this request as long as the performance can be figured out while handing off from the $match stage to the $search stage.

   Currently, I am re-writing my queries that were previously using $match + $text queries using $search + compound. Firstly, this is a fair bit of work depending on the number of match clauses etc. Secondly, not all the operators that $match supports are supported inside $search/compound clauses causing product differences.

   Anything that would speed up migrating $match queries to use $search while maintaining query results would help take advantage of the $search capabilities without having to rework the entire query logic.

   As a side note, I'm aware that $match can follow a $search stage, but unfortunately this is really not… more

   7 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

4. Save pipelines to run in aggregation mode

   A Button to save pipeline in aggregation tab and run this saved pipelines.

   7 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
   under review  ·  Rez responded

   Danilo – Great idea. We are reviewing it at the moment. Just curious whether you use the agg tab to do adhoc analysis or test queries which you eventually put in your app?

5. 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.

   6 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

6. Support full Lucene Query Parser syntax in $search

   I’m looking to expose “power user” queries through our UI, but the queryString operator only works on string data types, and is somewhat too simplistic for this purpose.

   Obviously, accepting raw user inputs and directly building a query from it is a security risk, but using something like queryString (which I do currently) seems like a safer and/or easier option.

   I would like to see a new $search operator (perhaps "lucene" or "query") that accepts the full Lucene Query Parser Syntax.

   https://lucene.apache.org/core/2_9_4/queryparsersyntax.html

   6 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

7. Support min-max computation for number and date fields, within Atlas Search

   Currently, the $min and $max aggregation operators can be used in a number of aggregation pipeline stages, in order to find min/max values for fields. It would be great if either these operators were supported within $search, or if there was a way to compute the min-max values for number and date fields within Atlas Search itself. There are certain use-cases where such a functionality can prove useful.

   For instance, we can leverage the $near operator to get sorted results, and determine the sort order of the results based on the origin. However, many times, the min-max values for the field might not be known beforehand, and thus determining what value of "origin" to use in the query can be challenging. However, if there was a way to compute the min or max of a field within $search itself, then it would really be helpful for those use-cases. If such a functionality were implemented, it could be used in a way that could be something like this:

   near": {
                   "origin": "max" / "min",
                   "path": "rating",
                   "pivot": 1
   }
   

   Currently, the $min and $max aggregation operators can be used in a number of aggregation pipeline stages, in order to find min/max values for fields. It would be great if either these operators were supported within $search, or if there was a way to compute the min-max values for number and date fields within Atlas Search itself. There are certain use-cases where such a functionality can prove useful.

   For instance, we can leverage the $near operator to get sorted results, and determine the sort order of the results based on the origin. However, many times, the min-max values… more

   6 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

8. Use case driven search operators and index types

   Examples: phone numbers, addresses, websites, emails

   If this would be helpful for you, please comment the data type you are looking for

   6 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

9. Atlas Search for Online Archive

   As a user of Online Archive, I would like full text search capabilities from Atlas Search available to me.

   6 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

10. Index Templates

    I'd like the ability to apply index templates or field level mappings for my indexes

    5 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

11. Introduce the ability to "forecast the Atlas Search index-size" in advance, before starting the index build

    Currently, prior to building an Atlas Search index, there is no way for users to know how large that index can get. Knowing the projected-index-size in advance can especially be helpful for users who might need to build index on a large collection, and where building such an index can push the disk-utilization to the max.

    Therefore, this is a feature request to implement a way to "forecast the Atlas Search index-size" in advance, before starting the index build.

    5 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

12. Allow to create Atlas Search index on a not existing collection

    Currently it is not possible to create an Atlas Search index on a not existing collection, this makes more complicated to automatise the index creation on new clusters (e.g. via terraform).

    Would be nice to allow the implicit collection creation when creating an Atlas Search Index.

    5 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

13. Percolator/reverse search

    Ability to store queries that allow you to supply a document and return the queries that match it.

    5 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

14. New Analyzers

    Customer is asking about adding new Analyzers language for Polish , Slovenian, Slovak and Croatian .

    5 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
    planned  ·  Marcus Eagan responded

    We have planned to add more analyzers.

15. Provide the ability to auto-scale dedicated search nodes

    Currently, dedicated search nodes in Atlas Search cannot be auto-scaled. This is a feature request to introduce the ability to auto-scale dedicated search nodes.

    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

16. Support for fuzzy search and synonyms

    it is just possible to either, use synonms, or fuzzy search. Would be great to have both options in one search query

    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

    under review  ·  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

17. Provide a button to cancel in-progress index builds

    Currently, the only option for cancelling an in-progress index build is to delete the index using the "Delete Index" menu-item in the Search Tab, or by using the Delete an Atlas Search Index API. This however is not easily evident, if users want to cancel an index build for any reason.

    Therefore, this is a feature request to provide a button to "cancel" in-progress index builds from the Atlas UI.

    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

18. Ability to set a "minimum should match" in a query

    I can specify a percent of terms I want to match, for instance 100% means require all terms, 66% means, only return documents that matched at least 60% of the terms. (the default is 1 term)

    Ex for 100%

    search "foo bar"

    "foo bar" "bar foo" "bar hello foo" would all return

    "foo hello" would not

    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

    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

19. Percolator for Atlas search to support Reverse look ups

    Percolator for Atlas search to support Reverse look ups for real estate property data

    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

20. Allow the option to mention the number of search results needed

    I would like to get only the top scored 1000 or 2000 records while doing the search. Currently this is 2 step process : $search and then use the $limit stage.

    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

    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