Skip to content

Atlas Search

← MongoDB Feedback Engine

Tell us how to improve Atlas Search!

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

    77 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    10 comments  ·  Admin →
    declined  ·  AdminAmy (Admin, MongoDB) responded

    This functionality can be achieved with the compound operator. For an example of searching multiple fields with the autocomplete operator, see the Advanced Example in this tutorial.


    Please let us know if you have any questions or additional feedback about this solution.

  2. Allow $match or $sort stages that follow the $search stage to use MongoDB native indexes

    Currently, if there are $match or $sort stages that follow the $search stage, then those $match and $sort stages are unable to use MongoDB's native indexes on the fields being matched/sorted.

    While the documentation recommends 1) designing your $search query so that all necessary filtering occurs in the $search stage which removes the need for a $match stage and 2) instead of using a $sort stage, using the $near operator to sort documents based on a numeric, date, or geo field, such changes are not always feasible depending on the use-case. In such instances, having a $match and …

    11 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    0 comments  ·  Admin →
    declined  ·  Elle responded

    The spirit of this request is to provide faster sorted results with Atlas Search. Efficient sorting of results when using Atlas Search is an important use-case to us and that we are proactively exploring what features we can provide in this regard. After reviewing with the engineering team, we've determined that this particular approach will not provide the intended benefits so we will not be pursuing it.  Please follow Faster Sorting with Atlas Search for future developments. 

  • Don't see your idea?

Atlas Search

Categories

Feedback and Knowledge Base

(thinking…)