Atlas Search
-
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.
61 votesWe’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. :-)
-
Allow autocomplete search on an array of strings
Currently, one can't use the autocomplete type to index fields whose value is an array of strings. This is a feature request to allow autocomplete indexing and searching on an array of strings.
13 votesSorry for the miscommunication, this feature is not yet available but will be in the near future. Thank you for your patience and keep following this ticket for updates.
-
Allow $elemMatch inside $search
When searching array of objects inside document, it'll be useful if we have a similar operator like $elemMatch
3 votesWe currently do not support all data types within in documents that are nested in arrays. We will support more functionality with compound filter that is similar to elem match in the future.
For now, consider your data model and check out: You can use the filter query to achieve very similar functionality as seen here: https://docs.atlas.mongodb.com/reference/atlas-search/compound/#filter-example
-
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.
10 votes -
Faster Faceting
Current faceting solution is not fast enough for search use cases for larger datasets.
34 votesAtlas 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.
-
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
11 votesThis work has started and I will inform the team when this feature is released. It’s coming soon.
-
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.
12 votesWe 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. :-)
-
I need to be able to search for dates and numbers in arrays
I have sets of results which contain dates and I need to be able to search from within them. For example:
{ experience: [ { name: "Abc", startDate: ISODate("2019-01-01T00:00:00.000Z"), startDate: ISODate("2020-01-01T00:00:00.000Z") }, { name: "Xyz", startDate: ISODate("2018-01-01T00:00:00.000Z"), startDate: ISODate("2019-01-01T00:00:00.000Z") } ] }So I need to be able to do a
nearsearch acrossexperience.startDatevalues, for example.The Date mapping documentation (https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#date) says:
A date cannot be indexed if it is part of an array.
And while the number documentation doesn't mention the same restriction by experimentation I have found it has the same resriction (strings dont…
22 votesWork on this feature has begun. Let us know if you have any questions.
-
Perform a search over multiple collections
Right now you can only search over one collection. I'd like to be able to search over several collections at the same time.
49 votesThe work on performing a search over multiple collections started a while ago and we will update you here when it is released.
-
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/
34 votesWe have started this work. Please stay tuned for an announcement about its completion.
- Don't see your idea?