Atlas Search
55 results found
-
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.
-
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
-
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 -
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.
-
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 -
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.
-
Deploy Atlas Search from Terraform
Add the necessary resource types to the mongodb_atlas Terraform provider to enable Atlas search indexes to be deployed by Terraform. This is needed as we need MongoDB apikey to call the API.
5 votesWe’ve released an integration with Terraform – feel free to utilize this documentation: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/search_index
Please let us know any feedback you may have.
-
Faster Faceting
Current faceting solution is not fast enough for search use cases for larger datasets.
38 votes -
Add support for creating and editing Custom Analyzers via the Visual Editor
The Visual Editor currently does not support creating or editing custom analyzers. This is a feature request for adding support for creating and editing Custom Analyzers via the Visual Editor.
1 voteCustom Analyzers are now supported in the Visual Index Builder (changelog).
-
Reverse Search using edgeGram in autocomplete searches
For searching on the last few characters of a field's values, currently the only option available is to create a nGram or need to create a custom analyzer with regex split/capture group.
As lucene internally has the reverse option available, can we have reverse flag provided with edgeGram to perform searches from the end?
Use case:
Lets suppose the field is tokenNumber and we usually search by the last 5 digits of the tokenNumber itself.
1 voteWe recently released support for this feature in our latest autocomplete improvements: https://docs.atlas.mongodb.com/reference/atlas-search/autocomplete/
-
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.
-
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
-
The equals operator should support date datatype
Currently, for querying on "date" datatypes, we can only use "range" or "near" operators. The "equals" operator supports querying only "boolean" and "objectId" values, and not date values.
If we want to do equality based matching for date datatypes, then we can leverage "range" using "gt" and "lt" to find it. However this might be sub-optimal in some cases.
Therefore, this is a feature request for having equals operator support date datatype (in addition to boolean and objectId).
3 votesThis is available already; see documentation.
-
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.
-
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 -
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
-
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.
-
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!
-
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
- Don't see your idea?