User Manual Manage Indexes in Collection View Back to User Manual
Wildcard indexes can be useful when documents in a collection have variable fields and query patterns are not known in advance. When query patterns are known, a targeted Standard index is usually easier to evaluate and maintain.
For detailed information about Wildcard index behavior and supported options, see the Azure DocumentDB documentation.
$** key.metadata.$**.Use All fields when the index should cover fields throughout the document. Use Parent path when only one nested area of the document needs flexible indexing.
Use Projection to limit an all-fields Wildcard index to selected paths, or to exclude selected paths. An empty projection does not restrict the index.
Wildcard indexes have different restrictions from Standard indexes. The form validates incompatible selections and shows the available choices for the selected scope.
Use Preview as JSON to verify the generated definition. Use Playground or Shell when you want to modify the generated command before running it.