On this page本页内容
planCacheSetFilter
¶Set an index filter for a collection. If an index filter already exists for the query shape, the command overrides the previous index filter.
The command has the following syntax:语法如下所示:
The planCacheSetFilter
command has the following field:
planCacheSetFilter |
string | The name of the collection. |
query |
document | The query predicate associated with the index filter. Together with the Only the structure of the predicate, including the field names, are significant; the values in the query predicate are insignificant. As such, query predicates cover similar queries that differ only in the values. |
sort |
document | query and the projection , the sort make up the query shape for the specified index filter. |
projection |
document | query and the sort , the projection make up the query shape for the specified index filter. |
indexes |
array | An array of index filters for the specified query shape. Specify the index filters as either:
Because the query optimizer chooses among the collection scan and these indexes, if the specified indexes are non-existent or hidden, the optimizer will choose the collection scan. In cases of multiple indexes with the same key pattern, you must specify the index by name. |
comment |
any |
A comment can be any valid BSON type (string, integer, object, array, etc).
|
Index filters only exist for the duration of the server process and do not persist after shutdown; however, you can also clear existing index filters using the planCacheClearFilters
command.
A user must have access that includes the planCacheIndexFilter
action.
The following example creates an index filter on the orders
collection such that for queries that consist only of an equality match on the status
field without any projection and sort, the query optimizer evaluates only the two specified indexes and the collection scan for the winning plan:
In the query predicate, only the structure of the predicate, including the field names, are significant; the values are insignificant. As such, the created filter applies to the following operations:
To see whether MongoDB will apply an index filter for a query shape, check the indexFilterSet
field of either the db.collection.explain()
or the cursor.explain()
method.
The following example creates an index filter for the orders
collection. The filter applies to queries whose predicate is an equality match on the item
field, where only the quantity
field is projected and an ascending sort by order_date
is specified.
For the query shape, the query optimizer will only consider indexed plans which use the index { item: 1, order_date: 1, quantity: 1 }
.