Atlas Search
58 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.
-
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
-
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.
-
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.
-
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.
-
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
-
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!
-
Atlas Search index creation/validation improvements
Right now the tooltips that show errors during the search index are small and uninformative and don't really tell me what part of my index definition is wrong. I am spending a lot of time in the docs trying to find where my index structure is wrong. I'd like better error messages or more on-page guidance on how to structure things like custom analyzers.
2 votesThis feature is now available in the Atlas Search JSON Editor.
-
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 -
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).
-
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 -
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!
-
Date proximity search
We are building a ticket brokering system and showing the best events closest to a customers desired date is essential. Would love to see date proximity scoring.
1 voteThis is now live. See the docs at:
https://docs.atlas.mongodb.com/reference/full-text-search/near/
and
https://docs.atlas.mongodb.com/reference/full-text-search/range/
-
Add support for GeoJSON data
We are looking to build a directory for patients to find doctors, but it appears that Atlas Search does not yet support geographical data relevance. Any chance this is coming soon?
1 vote -
Allow ability to create autocomplete indexes
I want to be able to create an autocomplete index so that I do not have to build one for my typeahead search to work.
0 votesThis feature is live: https://docs.atlas.mongodb.com/reference/atlas-search/autocomplete/
- Don't see your idea?