Atlas Search
44 results found
-
Allow $count and $sort inside $search
Make $count and $sort directly with mongot, and dont lose time between mongot and mongodb.
119 votesAt 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.
-
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.
54 votesLeverage $unionWith and $lookup to run search queries against multiple collections or create a materialized view prior to indexing. View tutorials here.
-
The equals operator should support numeric datatypes
Currently, for querying on "number" datatypes, we can only use "range" or "near" operators. The "equals" operator supports querying only "boolean" and "objectId" values, and not numeric values.
If we want to do equality based matching for number datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases (such as when performing equality match on decimals).
Therefore, this is a feature request for having equals operator support numeric datatypes (in addition to boolean and objectId).
49 votesDocumentation can be found here
-
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/46 votesSort in Search is now GA -- see changelog here for documentation.
-
Allow Atlas Search indexes to be restored across clusters
Currently, when an Atlas backup snapshot from one environment is restored to another environment, it does not transfer or replicate the Atlas Search indexes from the source cluster to the destination cluster. As a result, after the snapshot is restored, the Atlas Search indexes have to be manually created on the collections in the destination cluster.
This is a request for a functionality that will allow a snapshot-restore from one cluster to another to also replicate the Atlas Search indexes from the source cluster to the destination cluster.
46 votesAtlas Search index definitions are now included in Cloud Backup snapshots of M10 or higher clusters. See Atlas Search Changelog.
-
Faster Faceting
Current faceting solution is not fast enough for search use cases for larger datasets.
38 votes -
Be able to create Search indexes from Mongo shell
Right now it seems like I can query indexes from the mongo shell but not create them, unless I am missing something in the docs?
32 votesThis feature is now available for Atlas M10+ clusters running MongoDB 6.0.8 or later. See July 10, 2023 changelog and documentation to learn more.
-
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
near
search acrossexperience.startDate
values, 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…
25 votesComplete, view changelog for more information
-
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 votesThis project was completed recently and you can read about it here: https://docs.atlas.mongodb.com/reference/atlas-search/autocomplete/
Not only did we add support for most languages that we support, but we also introduced reverseEdgeGram to support languages like Kurdish and Urdu. Please don’t hesitate to reach out 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.
17 votesCompleted, view changelog for more info
-
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 votesWe have released synonyms.
Index docs: https://docs.atlas.mongodb.com/reference/atlas-search/synonyms/
Query docs: https://docs.atlas.mongodb.com/reference/atlas-search/text/#definition
-
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
16 votesYou can achieve this functionality by using setting the autocomplete field mapping's `analyzer` field to lucene.keyword (see example) or a custom analyzer which uses the uaxUrlEmail tokenizer.
-
Search Query Analytics
For Atlas Search, I'd like to see data about what queries are run, and how many results are returned for a given query.
15 votesIn public preview, please let us know your feedback! See changelog here.
-
Functionality that provides details of how a score was calculated for an individual document
Every document returned by an Atlas Search query is assigned a score based on relevance. Many factors can influence a document's score, including the position of the search term in the document, the frequency of occurrence of the search term in the document, the type of operator the query uses, the type of analyzer the query uses, etc.
We do have an explain functionality in Atlas Search, which returns information about the $search query plan and execution statistics. The results returned by explain("executionStats") has a section on score, which provides statistics related to scoring documents in the result set. However,…
14 votes[Changelog] Added scoreDetails boolean option to retrieve a detailed breakdown of the score for each document in the query results.
-
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 votesSorry for the delay! this has been available for a while in the Atlas UI metrics tab. See all available metrics here.
-
support for the storage and high speed search of dense vectors (i.e. word embeddings)
One feature I would like to see in mongoDB is the support for the storage and high speed search of dense vectors (i.e. word embeddings). This feature, in combination with full text search, would bring mongoDB within parity with Elasticsearch and help us simplify our architectures for these types of solutions.
https://www.elastic.co/blog/text-similarity-search-with-vectors-in-elasticsearch
12 votesAtlas Vector Search is now available as a public preview in MongoDB Atlas.
-
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 -
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: globesIt would be great if we could do something like
path: products.*
query: globes8 votesWe’ve released the Wildcard Path feature in Atlas Search. You can read about it here: https://docs.atlas.mongodb.com/reference/atlas-search/path-construction/#wildcard-field-search
-
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 votesThis feature has been completed and released in the latest release of Atlas Search.
You can read the documentation here:
https://docs.atlas.mongodb.com/reference/atlas-search/analyzers/custom/
-
Add ability edit query syntax in Atlas UI
Right now you can only test simple queries in the Search Tester. I'd like to edit the query syntax to test more complex queries without the need to connect the cluster through Mongo Shell.
6 votesYou can now edit the Search Tester query to run any $search query.
- Don't see your idea?