Atlas Search
46 results found
-
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.
-
case insenstive sorting in atlas search
we need a way to get results back from an atlas search that will be case-insensitive.
currently, we need to index many columns with an upper option just to cover this need.
we looking for the same level of support that ELK has.2 votesThis can be achieved by using the normalizer: lowercase option in the token field mapping. See Case-Insensitive Sort tutorial here.
-
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
-
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.
-
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
-
Support for fuzzy search and synonyms
it is just possible to either, use synonms, or fuzzy search. Would be great to have both options in one search query
4 votesBelated post: Support for both exist
-
Allow autocomplete on nested document field
Although I can index a nested field using the autocomplete type, it does not return any results when queried.
Here's an example snippet from an index definiton:
"Customers": { "dynamic": false, "fields": { "Name": { "foldDiacritics": true, "maxGrams": 8, "minGrams": 3, "type": "autocomplete" } }, "type": "document" },In the above example, for a customer named "John Smith" I'd expect to get a result for "joh" when querying on the Customer.Name path. But I currently get no results.
2 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 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.
-
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
-
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/
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 -
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
-
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.
- Don't see your idea?