Atlas Search
52 results found
-
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.
-
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. :)
-
Atlas Search Query Profiler/Explainer
Similar to How in MonogDB you can perfrom db.collection.find().explain() or how in Elastic you have the Explain API (https://www.elastic.co/guide/en/elasticsearch/reference/current/search-explain.html)
It would be great to know how scores are arrived at in Atlas Search.
6 votesHi all,
The explain feature for Search has been released. There are more features for Search explain coming. You can read about:
https://docs.atlas.mongodb.com/reference/atlas-search/explain/
-
Function scores for Search
Elastic allows you to do to function scores, which allow us flexibility in manipulating results during certain queries. is this coming to Atlas Search?
https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html
6 votesWe now support a variety of function scores including constant, arithmetic, gaussian, path, score, and unary operators.
-
Support querying with numeric arrays (like $in)
I want to be able to query for multiple numbers in the same query without having to specify separate “range” clauses (or “equals” when they are supported with numbers).
ie. I want to be able to query for [1, 2, 3] and any document which matches 1, 2, or 3 gets returned.5 votesIncluded in our May 26th release, see docs and changelog here
-
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.
-
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 -
Allow $elemMatch inside $search
When searching array of objects inside document, it'll be useful if we have a similar operator like $elemMatch
4 votesCompleted, view changelog for more info
-
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/
-
Add $search to aggregation pipeline builder in Atlas
Right now I can write shell queries and Compass queries that can leverage $search in the aggregation pipeline, but not in Atlas.
4 votesThis feature has been implemented on Atlas.
-
MongoDB University Course on Atlas Search
I'd like to see a MongoDB university course on Atlas Search
3 votesVisit our university course here: https://learn.mongodb.com/courses/mongodb-atlas-search
-
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 -
Support M10/M20
We'd like to use this feature but it's currently not available.
3 votes -
Support sorting by the search relevance when custom sorting search results.
Our search index is mostly data, so we get a lot of documents with identical search relevance. We would like to use the newly announced sort feature, but we need to retain the sort relevance (score) as the primary sort criterion. We want to additionally specify reverse chronological order as the secondary criterion. Adding the missing ability to also sort by the score would solve our need.
2 votesCompleted in our September release. See changelog here.
- Don't see your idea?