Atlas Search
51 results found
-
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.
-
Allow $count and $sort inside $search
Make $count and $sort directly with mongot, and dont lose time between mongot and mongodb.
118 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.
-
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 -
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.
-
Add support for UUID datatypes in Atlas Search
Currently, UUID is not one of the supported datatypes for Atlas Search. This is a feature request to add support for UUID datatypes in Atlas Search.
52 votesThis work is now complete. Update your search index to:
1. Index fields using the uuid field mapping type
2. Query using the equals or in operators
3. You can also sort on UUID fields
-
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 -
Full-text search for Chinese language
Currently to perform full-text search for Chinese text, the mongo documents need to uploaded to Solr or ES. It would be helpful if the functionality can be supported by Atlas.
2 votesWe’ve added support for the Chinese Language via the Lucene CJK analyzer. You can learn more about it here: https://docs.atlas.mongodb.com/reference/atlas-search/analyzers/language/#ref-language-analyzers
-
Allow managing Atlas Search index via drivers
Currently I need to manage my indexes via the Atlas Search API but I would like to manage them using drivers in the same way that I manage all of my other MongoDB indexes.
34 votes -
Faster Pagination
I would like be able to paginate through search results faster.
96 votesPerformant sequential pagination in Atlas Search is now available on MongoDB clusters 6.0.13+ and 7.0.5+ to power Infinite Scroll, Load More, and Next/Previous Page application experiences. To specify where in your Atlas Search results to start returning results from, 1) generate Base64-encoded tokens for each document within your results using the new $meta keyword searchSequenceToken, and 2) use that token as a point of reference with the new searchBefore and searchAfter options within the $search stage.
For use cases not addressed by Sequential Pagination, please vote here.
-
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.
-
Support HTML strip tags analyzer
If some html text is indexed we could strip tags so searches by h1, span, div, etc... should not return results.
For example:
Elasticsearch: https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-htmlstrip-charfilter.html
2 votesWe have added this capability as a character filter via the release of custom analyzers:
https://docs.atlas.mongodb.com/reference/atlas-search/analyzers/custom/#htmlstrip
Please let me know if you have any questions and enjoy!
-
Faster Faceting
Current faceting solution is not fast enough for search use cases for larger datasets.
38 votes -
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…
25 votesComplete, view changelog for more information
-
Support M10/M20
We'd like to use this feature but it's currently not available.
3 votes -
Support Japanese Analyzer in Atlas Search
We would like support for a Japanese analyzer in Atlas Search
1 voteThe CJK analyzer provides basic Japanese search capabilities—if there is a specific request for a certain type of analyzer please do create a new idea describing what is needed beyond the CJK capabilites!
-
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 votesThis feature has been implemented.
Index Definition
https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#booleanQuery Operator
https://docs.atlas.mongodb.com/reference/atlas-search/equals/ -
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 votesSee a variety of tutorials on how to achieve this here: https://www.mongodb.com/docs/atlas/atlas-search/tutorial/cross-collection-tutorials/
-
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 -
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/
-
Support ngrams and edge ngrams
We leverage ngrams and edgengrams in Elastic. We need to have these in order to perform the same searches in Atlas Search:
https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-ngram-tokenizer.html
https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-edgengram-tokenizer.html
6 votesWe have released this feature and you can learn about it here: https://docs.atlas.mongodb.com/reference/atlas-search/index-definitions/#bson-data-types-autocomplete
Let me know if you have questions about the new features for nGrams and edgeGrams. :)
- Don't see your idea?