Atlas Search

  1. Allow $count and $sort inside $search

    Make $count and $sort directly with mongot, and dont lose time between mongot and mongodb.

    119 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    At MongoDB World last week, we announced that faster counts are now available with sharded collections. 


    We also announced a feature called Stored Source Fields which help you achieve faster post-aggregation performance. You can use this feature to experience faster sorting with Atlas Search. 


    You can read more about these two features here.


    After trying Stored Source Fields, if it does not meet your performance requirements - please vote on this new feedback item. 

  2. Allow autocomplete to work with special characters and Asia languages

    Hello,

    We are now using Atlas Search, with a deep dive in this feature, we found out that it will be very cool to support "special characters" (such as @,-) and "Asia languages (such as Chinese)" for autocomplete. I think this is a requirement for many world wide companies. We can't allow a search engine which only cover a part of our clients because our business is with people form the whole world.

    Thank you in advance,

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Synonym support for search

    I'd like to be able to set synonyms for word in my search index, for example, making a search for "cerulean" redirect to "blue"

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Support highlighting with autocomplete operator

    Currently, highlighting is supported only with search, term, compound, and span operators, and this is documented in the highlighting documentation. Therefore, if highlighting is used with the autocomplete operator, then it results in an error like this:

    "Highlights can not be generated. Path: "####" is not stored statically or dynamically indexed."

    This is a feature request to add support for highlighting with the autocomplete operator.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Wildcard Atlas Search

    We put a large amount of data inside of Atlas Search but don't always know where a field actually exists. For example we might have a field that is indexed but is several objects deep, and without knowing the path notation to that field we can't find it.

    For example instead of

    path: products.christmas.decorations.tree.ornaments
    query: globes

    It would be great if we could do something like

    path: products.*
    query: globes

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Atlas Search Custom Analyzers

    We want the ability to create our own custom analyzers in Atlas Search. It seems like the option might be there as there is a Define Analyzers button but it is not documented and the syntax does not match what I would expect to be valid, resulting in an index that never finishes building.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Atlas Search Query Profiler/Explainer

    Similar to How in MonogDB you can perfrom db.collection.find().explain() or how in Elastic you have the Explain API (https://www.elastic.co/guide/en/elasticsearch/reference/current/search-explain.html)

    It would be great to know how scores are arrived at in Atlas Search.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Function scores for Search

    Elastic allows you to do to function scores, which allow us flexibility in manipulating results during certain queries. is this coming to Atlas Search?

    https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Deploy Atlas Search from Terraform

    Add the necessary resource types to the mongodb_atlas Terraform provider to enable Atlas search indexes to be deployed by Terraform. This is needed as we need MongoDB apikey to call the API.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Soundex/phonetic filter support

    We need support for Soundex or phonetic filters for our use cases so we can support searches for similar sounding terms. thank you!

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Add boolean as a search data type

    I want to search boolean fields in my search index, but currently hit an error when trying to specify boolean fields:

    "Your index could not be built: Could not resolve type id 'boolean'"

    When is boolean type support coming?

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Full Text Index over a view

    My organization has a few use cases where we have a service 'join' various docs and write them into a 'consolidated doc' in elastic search to support various nested query requirements. It would be great if we could use FTS on a mongo/atlas view as we could then eliminate the need for our data joining service and its associated latency and consistency issues.

    Also fyi - it appears this is 'possible' in the current Atlas portal/UI and via the API. You can define a full text index on a view - but it disappears after a minute or two.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Add $search to aggregation pipeline builder in Atlas

    Right now I can write shell queries and Compass queries that can leverage $search in the aggregation pipeline, but not in Atlas.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Allow for specifying language-specific analyzers for the autocomplete datatype

    Currently, the autocomplete data-type doesn't allow for specifying an analyzer, which means it uses the default standard analyzer. Now, the standard analyzer divides text based on word boundaries, making it language-neutral in most cases. However, currently, another language-specific analyzer cannot be specified for autocomplete.

    This is a feature request to allow for specifying language-specific analyzers for the autocomplete data-type in the index definitions, in order to fully support autocomplete searching in languages other than English.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Support M10/M20

    We'd like to use this feature but it's currently not available.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Allow autocomplete on nested document field

    Although I can index a nested field using the autocomplete type, it does not return any results when queried.

    Here's an example snippet from an index definiton:

      "Customers": {
        "dynamic": false,
        "fields": {
          "Name": {
            "foldDiacritics": true,
            "maxGrams": 8,
            "minGrams": 3,
            "type": "autocomplete"
          }
        },
        "type": "document"
      },  
    

    In the above example, for a customer named "John Smith" I'd expect to get a result for "joh" when querying on the Customer.Name path. But I currently get no results.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Reverse Search using edgeGram in autocomplete searches

    For searching on the last few characters of a field's values, currently the only option available is to create a nGram or need to create a custom analyzer with regex split/capture group.

    As lucene internally has the reverse option available, can we have reverse flag provided with edgeGram to perform searches from the end?

    Use case:

    Lets suppose the field is tokenNumber and we usually search by the last 5 digits of the tokenNumber itself.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Text Search with regex

    It would be great if Text Search allows us to query with regular expressions. E.g.

    mycoll.find({ $text: { $search: "super%"} })

    Thank you for considering my request.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    completed  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1
  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base