Skip to content

Atlas Search

6 results found

  1. Allow autocomplete search on multiple fields using a wildcard path or by specifying multiple fields in the path

    Currently, (unlike the text operator) the autocomplete operator does not accept a path which is an array of field names. Also, a wildcard path ("path": {"wildcard": "*"}) cannot be specified for an autocomplete query. Therefore, the only way to perform an autocomplete search on multiple fields is by using the compound operator.

    This is a feature request to allow autocomplete search on multiple fields by using a wildcard path or by accepting an array of multiple fields in the path.

    76 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    started  ·  Marcus Eagan responded

    We’ve heard your feedback loud and clear. We are starting this work now.

    Thanks for the feedback. We will update you when it is released very soon. Let us know if you have any questions. :-)

  2. Faster Sorting with Atlas Search

    I am looking to achieve a faster sort when using Atlas Search.

    Please comment if you tried Stored Source Fields and it did not meet the performance you were looking for.

    Stored Source Fields Docs:
    Index - https://www.mongodb.com/docs/atlas/atlas-search/stored-source-definition/
    Query - https://www.mongodb.com/docs/atlas/atlas-search/return-stored-source/

    38 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Faster Faceting

    Current faceting solution is not fast enough for search use cases for larger datasets.

    38 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Atlas Search facet and count are in preview. The features and the corresponding documentation may change at any time in the preview stage.


    The Atlas Search $searchMeta stage is not available on shared clusters. $searchMeta is available only on dedicated clusters.


    facet is only available on Atlas clusters running one of the following versions:

    • MongoDB 4.4.11 or later
    • MongoDB 5.0.4 or later


    You can't run facet queries with Explain.


    This ticket will be marked as complete when Facet is available on Sharded clusters. 

  4. Support for nested datatype search

    It appears that Atlas Search does not yet support nested documents in arrays like MongoDB

    https://docs.mongodb.com/v4.2/reference/operator/query/elemMatch/

    37 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Allow autocomplete to work with email addresses.

    At the moment, an autocomplete index does not tokenize the "@" in email addresses. So when using an autocomplete search on an email address field, the search breaks as soon as the "@" is entered.

    I started a thread in the community about this very issue.

    https://developer.mongodb.com/community/forums/t/mongo-search-autocomplete-type/10561/5

    15 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    started  ·  Marcus Eagan responded

    This work has started and I will inform the team when this feature is released. It’s coming soon.

  6. Metric for Displaying Search Index Consistency Lag

    I would like a metric that shows me what the latency is between the state of the MongoDB collection and the Search index in Atlas.

    The difference between the optime of the collection and the optime of the Search index would be the latency. Please consider exposing this metric.

    13 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  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    started  ·  Marcus Eagan responded

    We heard you loud and clear! This work has been started, though it is not so simple. I will update the group when it is complete and share a bit of instructions on how to interpret the metrics in case anything is unclear. Thank you all for being so vocal about the future of your product.

    Please don’t hesitate with any questions. Keep in mind, the search index should be largely up to date with the database as we are really close by. :-)

  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base