Frequently Asked Questions
On this page
- Can I run partial string matching Atlas Search queries?
- Can I perform case-insensitive search with the
wildcard
orregex
operator? - Does
storedSource
support 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?
Can I run partial string matching Atlas Search queries?
Yes. The following Atlas Search operators support partial string matching queries:
Tip
Can I perform case-insensitive search with the wildcard
or regex
operator?
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:
Does storedSource
support case-insensitive collation on fields?
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 1
or
2
when you create it, and must not specify a different collation in
your queries and indexes.
Can I use the shard key to run Atlas Search queries on specific shard(s)?
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.
Do queries run on primary or secondary nodes?
By default, queries run on primary notes. You can configure your read reference or use replica set tags to specify read preference. To learn more, see Atlas Search Overview.