Atlas Search
153 results found
-
atlas search null
A string or number data type that has the value 'null' is returned and is not excluded even with filtering with query: 'null' entry. The $exists and $compound operators may benefit from excluding fields that have a value of 'null' but not exactly non-existent in a document.
2 votes -
Allow scoring with real word frequency (instead of word frequency per shard)
We are migrating from ES and there is an option when having a few documents to do a first query to return the term frequencies for all shards and then do the normal query using these frequencies to calculate the score.
The option is called "?searchtype=dfsquerythenfetch" and it's documented here: https://www.elastic.co/guide/en/elasticsearch/guide/current/relevance-is-broken.html.
It would be great to have a similar option in Atlas Search! Thank you
2 votes -
nested facets
in elastic we can do complex nested facet groups such as
"aggs": {
"resellers": {
"nested": {
"path": "resellers"
},
"aggs": {
"min_price": {
"min": {
"field": "resellers.price"
}
}
}
}
}It would be nice to see the same functionality in atlas search
2 votes -
Configure Alert "Insufficient disk space to support rebuilding search indexes" via API
Currently, it's not possible to configure the alert "Insufficient disk space to support rebuilding search indexes" via API (and therefor also not by terraform).
When setting the respective eventTypeName "HOSTDISKSPACEINSUFFICIENTFORSEARCHINDEX_REBUILD"
I get the following response:
400
request "INVALIDENUMVALUE"
An invalid enumeration value HOSTDISKSPACEINSUFFICIENTFORSEARCHINDEX_REBUILD was specified.The API should support this (and any other alerts configurable by the UI).
2 votes -
Configure Search Relevance or Results Ordering in the UI
I want to be able to configure search relevance or the order of results with a n Atlas UI module and no code.
2 votes -
Query_syntax operator should support lucene syntax
At the moment the query_syntax seems to have a custom syntax. It looks similar to lucene syntax but is not the same.
There are a few differences to azure and elastic and I don’t understand whether I am doing something wrong or not.
What all three service have in common is that they are built on top of lucene, therefore I though that the querystring operator uses the lucene query syntax as it seems to be done by elastic and azure: https://lucene.apache.org/core/29_4/queryparsersyntax.html
Documentation about the elastic query string query can be found under: https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html
There are a few…
2 votes -
API to list all Atlas Search Indexes configured across all collections in the cluster
Currently, there is an API to list all Atlas Search indexes configured for a specific collection. However, there is no API that lists all Atlas Search indexes configured across all collections across all databases, in a particular cluster. The Atlas UI shows this, but the Atlas API does not have that functionality.
This is a feature request to add the API capability to list all Atlas Search indexes configured on all collections in a cluster.
2 votes -
2 votes
-
Allow ability to exclude specific fields from Atlas Search
In order to reduce index size and improve performance, we should be able to exclude specific fields from the Atlas Search index.
2 votes -
Add truncate collection button, delete documents older than...
In the old interface we can truncate collections without using additional software, just using WEB GUI to keep small database size.
It would be nice to have the ability to delete older documents. This option is usable for IOT or medical implementations (Nightscout).2 votes -
Search Page User Interface
We would like to have a search page that automatically hooks up our Atlas Search indexes to our application.
2 votes -
toggle or autohide left side menu and upper menu while
add a toggle button to minimize the width of menus taking the larger part of the screen while working with a specific cluster.
2 votes -
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 -
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 for time series collections
It would be nice if we could use atlas search on a time series collection
1 vote -
Atlas Search equivalent for "should" but ignoring score
Currently to perform an "OR" check in an Atlas Search query the only available operator is "should" which contributes to score.
I propose "ought" the equivalent operator, but doesn't contribute to score.
Alternatively, I suggest an option to $search to omit score entirely, this could offer a little performance boost on large document set by removing the need to track score when it is not needed.
1 vote -
allow atlas search for serverless instances
As of now, atlas search is not allowed for serverless instances, but many people using serverless instances and they atlas search to perform some advanced search queries.
1 vote -
1 vote
-
Atlas search Index is not updating.
Each time I perform CRUD operations in my collection, the Search Index doesn't update immediately. Instead, it takes a considerable amount of time. This issue significantly hampers the progress of my project. Any suggestions for improvement would be greatly appreciated.
1 vote -
1 vote
- Don't see your idea?