Atlas Search
149 results found
-
Allow indexing of synthetic fields
In order to work around some of the inherent limitations of the Atlas Search capabilities, it would be very useful if we could define and index arbitrary synthetic fields using any normal MongoDB functions & operators. All other Atlas Search capabilities (query, sort, etc.) should support these synthetic fields the same as any other.
This could possibly be implemented with a new field type and a custom analyzer that supports an aggregate pipeline on the input document and returning the field as its output. This is just an idea, there may be better ways to do it.
…{ "mappings": {2 votes -
Sort by a specific array index
When creating indexes and sorting with "normal" queries, it is possible to index/sort on a specific array index (e.g.
foo.0.bar). I do this because the search results grid in our UI only has room to show the firstfoo.barresult, so it doesn't make sense visually to sort by additional objects which the user can't see.Since the new Atlas Search Sort syntax looks the same, I was hoping to do that with it as well, but it doesn't seem possible.
Example:
…[ { "xyzzy": "xyzzy", "foo": [ { "bar": "A" } ] }, { "xyzzy": "xyzzy", "foo": [2 votes -
Data type coercion when document field type doesn't match index field type
When a document field type doesn't match the index field type, it seems to be indexed as "blank" and won't match anything. Many data types are readily convertible between type representations. It would be great if Atlas Search could do that for us and would open up richer functionality by allowing us to use operators/analyzers/etc. on types that don't normally support them.
My particular use case is to allow searching & sorting on numbers stored as strings. When creating indexes and sorting with "normal" queries, it is possible to sort numbers stored as strings by their numerical ordering rather than…
1 vote -
Text Analysis for Field Mappings
Show how an indexed document and query terms get analyzed to produce tokens based on my field mapping configuration.
1 vote -
Feedback on the Atlas Search Visual Index Builder
How can we improve?
1 vote -
Allow faceting on boolean fields
Right now you can only facet on string, number, date fields.
https://www.mongodb.com/docs/atlas/atlas-search/facet/#facet-definitionI would like to also be able to facet on boolean fields.
6 votes -
Synonyms support for autocomplete operator
Hi.
Having synonyms support for the autocomplete operator would be great! Is this possible?
Best regards,
Tim1 vote -
Add option for specifying OR or AND when using multiple terms in autocomplete search string
Hi.
Currently the autocomplete operator handles multiple terms in a query string as OR, not AND. That means that one of the terms should match, not all of them.
An option for specifying how multiple terms should be handled by the autocomplete operator (if one of the terms should match (OR) or all of them should match (AND)) would be great!
So having an AND handling would mean the more terms I add to the search string the more specific the results will be. With OR it's the other way around.
Thanks!
Best regards,
Tim1 vote -
Atlas Search on serverless instances
Hi,
I'd like to use Atlas Search on Atlas Serverless.
16 votes -
Additional function scores decay functions: exp & linear
Atlas Search currently only supports gaussian decay function for function scores. In 4 out of 5 of our use cases exp would be a much more natural choice.
Hopefully that is just a small task!
1 vote -
Allow comments in JSON code
It would be great if we could keep comments in JSON generated items such as indexes (both MongoDB and Atlas Search)
2 votes -
Allow indexing of only part of a collection
Would be great to be able to create an Atlas Search index that only indexes part of a collection (like partialFilterExpression for a regular index). This would be valuable in situations where a collection is quite large (which would create a lot of unnecessary overhead) but only a small fraction of it needs to be searchable.
2 votes -
Allow faceting for embeddedDocuments
At the moment embeddedDocuments does not allow number or date faceting.
In my opinion, this does not make the operator useful, since Faceting is now the standard for every search.
16 votes -
Support ObjectID as a datatype for search facets
I'm really interested in using search facets to boost search performance, but one of the fields that I want to filter by is an ObjectId.
I believe the only supported facet types are [date, numberFacet, stringFacet].
10 votes -
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
13 votesWork to address this has been scheduled.
-
Ruby on Rails support of Atlas Search index management
Feedback from customer: "Currently we need to manage core DB indexes and atlas search indexes separately. We'd prefer to manage them all in the Rails model code but MongoID only supports core DB index configuration. We're having to use terraform for atlas search index management."
1 vote -
Token filter that removes duplicated entries
Create a token filter or a tokenizer or even an option that removes duplicate words in fields to avoid misleading scoring. For example: if I insert a document with a property "Testing testing document", another with "Testing example" and a third with "Testing foo" and I search for "Testing foo", the first document receives a higher score.1 vote -
Multiple Capture Groups in RegEx Tokenizer
Currently the RegEx tokenizer only supports to either create a token from each match or for one capture group per match. This makes it impossible to reuse parts of the text for multiple tokens, for example when you want to tokenize "13.3" into "13" as well as "13.3" (our use case is searching products where we want to find a 13.3" device by searching for 13" as well as 13.3").
1 vote -
wildcard paths in index specifications
It would make index specification easier in some cases if wildcards were possible in the paths. Yes we have dynamic indexing, but to keep the index size minimal and to be more flexible I want to index only the fields I really need. Consider the following example:
Example document:
{
foo: {
de: {
field1: 'bar',
field2: 'bar'
},
en: {
field1: 'bar',
field2: 'bar'
},
fr: {
field1: 'bar',
field2: 'bar'
},
}
}Index specification:
{
"mappings": {
"dynamic": false,
"fields": {
"foo": {
"type": "document",
"dynamic": false,
"fields": {
"$**": {
"type": "document",
"dynamic": false,
"fields": {…1 vote -
Hierarchical/Multi-Level filters/facets.
As a user, I'd like to be able to compute faceted counts on multi-levels of categorization.
17 votes
- Don't see your idea?