On this page
- Can I run partial string matching Atlas Search queries?
- Can I perform case-insensitive search with the
storedSourcesupport case-insensitive collation on fields?
- Can I use the shard key to run Atlas Search queries on specific shard(s)?
- Do queries run on primary or secondary nodes?
- Why is my search index disappearing?
- Can I restore Atlas Search indexes from Cloud Backup snapshots?
- Does Atlas Search work with CSFLE encrypting clients?
- Can I query CSFLE encrypted data?
Yes. The following Atlas Search operators support partial string matching queries:
Yes. You can use the wildcard and regex operators with a custom analyzer to perform a case-insensitive search. You can define a custom analyzer with the following tokenizer and token filter to perform a wildcard case-insensitive search:
Yes. The Atlas Search storedSource option stores
original values. To perform case-insensitive operations after the
$search stage on the results returned using
returnStoredSource option, you
must set the default collation strength of your collection to
2 when you create it, and must not specify a different collation in
your queries and indexes.
No, you can't use the shard key to run Atlas Search queries on a specific shard or a subset of shards. In a sharded cluster environment, Atlas Search queries are scatter-gather queries that run on all the shards.
Double check that you entered the correct database and collection names. If you enter a non-existent database or collection name, the Atlas UI temporarily builds the index and deletes it shortly after.
If you use the
$outaggregation stage to overwrite your collection, you must delete and recreate your search index, as search indexes are not copied to destination collections. To learn more, see $out Index Constraints.
Yes, you can use CSFLE encrypting clients to run Atlas Search queries against data in MongoDB version 6.0 and later.
No, you can't query CSFLE encrypted data using Atlas Search.