Atlas Search
153 results found
-
More useful query error
When you enter a query, if there is any kind of syntax error, you get dumped to a page where your only option is to return to clusters. Then you need to renavigate to your db and collection to attempt a new query.
This is really frustrating as instead of just being able to go back and correct your mistake, you must start writing the query again from scratch.
Why not put users back where they were and restore the query they were attempting so it can be easily fixed? Or better yet, check the query before you try to…
1 vote -
Disable alerts during search index builds
We're building a full-text search index, and I guess that causes high CPU usage on the cluster. So I've been getting alerts pretty much every few minutes for about 16 hours. I went to "acknowledge" the alert, but since it's flapping, the acknowledgement gets removed when the CPU recovers, and then a new alert is generated a few minutes later.
I would like to be able to disable alerts during search index builds so that I am not spammed with emails.
0 votes -
import index definitions from SOLR or ElasticSearch
I don't want to have to write my index definition over again. Is there a way I can import or transform it so that my existing definition can just work?
1 vote -
Allow search users to bring their own encryption key
I want to use my own encryption key so I know that my search data is encrypted with credentials I manage myself
4 votes -
API to know if FTS is enabled on a collection
As of now I can't find a way to detect whether a collection has FTS enabled or not. Indexes are not shown on the indexes() API. In a multi environment context, we usually want to implement a fallback implementation using another text search option when FTS is not available (dev or staging env for instance).
By not having an API to know if it's available or not, you can throw $searchBeta functions in a pipeline on cluster without FTS. It won't fail but you'll get no results. You cannot differentiate that from a true empty result set.
0 votes -
Allow the ability to test Atlas Search locally
We need text search to "somehow" work locally and ci.
We've a multiregional team and development has to continue if there are internet problems in one of our offices.
Our workflow consists of :
unitTest using in-memory-mongodb
local testing, using the developers local mongo instance
test env testing with a QA team (using atlas, but <30m)
production launch
With the current feature set, the first time we can test a feature is on production. Even if low-tier availability was there the other two issues are blockers as we won't just ditch TDD for textSearch.
358 votesNow in Public Preview: Introducing a Local Experience for Atlas, Atlas Search, and Atlas Vector Search with the Atlas CLI
Please feel to reply with feedback or leave comments. Happy to connect directly and include your team in our Early Access Program to provide additional help.
-
Support basic recommendations
In Elastic we leverage basic built-ins like "more like this" so we don't show zero results sometimes and also as a simple recommendation engine in cases we don't use our own custom recommendation logic
https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-mlt-query.html
1 vote -
Search Promo/Campaign management
In my company Marketing often wants to promote a search for a given period of time as a paid ad. I have to manually update the search index to do this; I'd love a way to just pin a search result to #1 for a period of time, like two weeks.
1 vote -
Support for nested datatype search
It appears that Atlas Search does not yet support nested documents in arrays like MongoDB
https://docs.mongodb.com/v4.2/reference/operator/query/elemMatch/
39 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 -
Add batch size configuration to Atlas Search
We have lots and lots of data we want to put in Atlas Search. In our experience this takes a lot of time and can overwhelm servers; we also want to be able to see as we upload data that our configuration is working.
1 vote -
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.
1 vote -
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
- Don't see your idea?