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

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.

I want to search boolean fields in my search index, but currently hit an error when trying to specify boolean fields:

"Your index could not be built: Could not resolve type id 'boolean'"

When is boolean type support coming?

Right now I can write shell queries and Compass queries that can leverage $searchBeta in the aggregation pipeline, but not in Atlas.

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'd like to use this feature but it's currently not available.

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?

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

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

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

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"

Right now Atlas Search highlighting only supports text in the sentence surrounding a match, ignoring any other sentences in a field that have also been indexed.

I would like to be able to change the default behavior to meet my needs.

Allow for the use of the $searchBeta operator in all SDKs

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?

I want to use my own encryption key so I know that my search data is encrypted with credentials I manage myself

My organization has a few use cases where we have a service 'join' various docs and write them into a 'consolidated doc' in elastic search to support various nested query requirements. It would be great if we could use FTS on a mongo/atlas view as we could then eliminate the need for our data joining service and its associated latency and consistency issues.

Also fyi - it appears this is 'possible' in the current Atlas portal/UI and via the API. You can define a full text index on a view - but it disappears after a minute or two.

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.

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