Atlas Search
141 results found
-
Reindex from a given place in our index
We want to be able to apply an index configuration change that we know applies only to new data we placed in our index a couple weeks ago. It appears we have to re-index the entire collection over again to apply our index config change. We'd love to just set a date and re-index for the next data just from that point in time if possible so we do not have re-index the entire collection
2 votes -
Return the amount of results in a Search query
I don't think there's currently a way to see this today? Seems like a missing basic feature.
2 votes -
Test plan/suite for Atlas Search
Other search services like Elastic have public benchmarks of different data types so we can determine how they should perform: https://benchmarks.elastic.co/index.html
Would love to see the same for Atlas Search.
2 votes -
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 votes -
Atlas can be configured to raise alert notification when the Atlas cluster already scales to the max tier.
Atlas can be configured to raise alert notification only when the Atlas cluster already scales up to the max tier allowed. This can be help to avoid notification spams which does not require operation team actions and focus on the critical resource consumption alerts like cpu, memory, disk IO.
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 -
Text Analysis in the Visual Index Builder
Show how an indexed document and query terms get analyzed to produce tokens based on my index configuration.
1 vote -
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 -
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 -
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 -
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 -
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 -
knnBeta Limitations and Syntax
I tested the new knnBeta operator today and it worked so far.
Can we expect the current operator limitations to be gone by release?
The current limitations make it virtually impossible to use the knn operator as a replacement for previous text operators (like text).
I would prefer the filter parameter to be omitted and knn not have to be a top-level operator.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 -
Ability to randomize score
I would like to be able to add randomness to the search results' score.
1 vote -
Ability to return all documents in a collection
I need to return all documents in a collection while boosting certain results which match my search criteria.
1 vote -
Ability to exclude documents matching a certain criteria from index
We don't do physical deletion of documents, but a logical one, flagging them by setting a value for a
deleted_atfield.We would like an option to exclude documents where that field exists and is not null from the index, because they will never be returned and are only consuming space of the index.
Currently we use a
mustNotcondition to exclude them, but of course they are still being indexed.The ideal would be to be able to define the exclusion criteria in the index definition.
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 -
Duplicate search index
I want to be able to easily duplicate a search index in the Atlas UI.
1 vote
- Don't see your idea?