Atlas Search
55 results found
-
Allow sort by boolean fields
When creating indexes and sorting with "normal" queries, it is possible to index/sort on a boolean field. I was hoping to do this with Atlas Search Sort as well, but it only supports date, number and token (string).
While workarounds are available (using custom scoring), these are not easily combined with multiple sort fields and make programmatically building a query vastly more complex.
3 votesThis work has been completed; see changelog and documentation.
-
Dedicated search nodes
Currently, Atlas Search (mongot) is collocated with Atlas (mongod) on the same database deployment. Today, I have to size their workload based on both search and database requirements, which introduces the possibility of resource contention between their database and search deployment. I'd like to scale my search deployment independently of my database deployment.
13 votesDedicated search nodes have been delivered for GCP and AWS. Azure will ship soon.
-
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.
-
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.
-
Add storedSource parameter to atlas admin API search index create/update to use with terraform
Right now it is impossible to create atlas search index via terraform with "storedSource" parameter. This brings a lot of inconvenience and configuration-related bugs.
Related issue
https://github.com/mongodb/terraform-provider-mongodbatlas/issues/871
15 votesStored Source Parameter in mongodbatlas_search_index resource and data source has now been released in Terraform. Users will need to upgrade to latest Terraform Atlas provider to be able to use.
For more details see here: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/search_index#stored_source
-
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
-
Extending Range operator support to ObjectId values
If the Range operator supports ObjectId, it'll be really useful for the application that sorts or paginates data using _id, since _id is sorted by default.
9 votesThis work has been completed; see changelog and documentation.
-
Allow indexing and querying for null datatype in Atlas Search
The null datatype is not amongst the datatypes that Atlas Search supports at this time. As a result, if the use-case is to perform a text search on some fields and perform an equality/inequality check on other field(s) to see if it is/isn't null, then we need to have a $match stage following the $search stage, which is detrimental to the query performance as documented here. This is an enhancement request to allow indexing and querying for null datatype in Atlas Search, to avoid the above scenario.
47 votesThis work is now complete. Update your search index to search for null using the Atlas Search equals operator on any field that is statically or dynamically indexed.
-
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 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
-
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.
-
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.
1 vote -
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.
-
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.
-
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.
-
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).
48 votesDocumentation can be found here
-
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 $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.
- Don't see your idea?