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.

Can we get Search on-prem? Is this always going to be an Atlas-only feature?

Currently $search is required to be the first stage in the aggregation pipeline. It would be more intuitive if we could use after other operators, such as $match.

We put a large amount of data inside of Atlas Search but don't always know where a field actually exists. For example we might have a field that is indexed but is several objects deep, and without knowing the path notation to that field we can't find it.

For example instead of

path: products.christmas.decorations.tree.ornaments
query: globes

It would be great if we could do something like

path: products.*
query: globes

Right now you can only search over one collection. I'd like to be able to search over several collections at the same time.

We want the ability to create our own custom analyzers in Atlas Search. It seems like the option might be there as there is a Define Analyzers button but it is not documented and the syntax does not match what I would expect to be valid, resulting in an index that never finishes building.

We leverage ngrams and edgengrams in Elastic. We need to have these in order to perform the same searches in Atlas Search:

https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-ngram-tokenizer.html

https://www.elastic.co/guide/en/elasticsearch/reference/current/analysis-edgengram-tokenizer.html

Right now it seems like I can query indexes from the mongo shell but not create them, unless I am missing something in the docs?

Current faceting solution is not fast enough for search use cases for larger datasets.

It appears that Atlas Search does not yet support nested datatype like ElasticSearch does:

https://www.elastic.co/guide/en/elasticsearch/reference/current/nested.html

We need this for our application

We have a large collection but would only like to index the most recent entries, which would reduce the amount of space and resources it would take to index and query.

Elastic allows you to do to function scores, which allow us flexibility in manipulating results during certain queries. is this coming to Atlas Search?

https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-function-score-query.html

I'd like to be able to set synonyms for word in my search index, for example, making a search for "cerulean" redirect to "blue"

Enable indexing and querying of near and range operators for Decimal128.

We have unstructured text and would like Atlas Search to detect important entities so that we can use them for relevance and ranking

We have scanned images with text, and would like to have OCR capabilities so that we can search against those images

Right now, managing stop words is a very manual process.

Provide tools to easily add Atlas Search to index and search our website.

It is difficult to rank search results just using scores. There should be better tools for managing rankings.