The index selector currently believes that hashed, sparse indexes can be used to answer {$exists:false} queries. However, sparse indexes cannot be used to answer such queries so this triggers a failure.
A resolution to this ticket would include:
1) server changes that disallow sparse hashed indices from being considered to answer such a query
2) unit tests and javascript tests ensuring that hashed sparse indexes won't be considered to answer {$exists: false} queries
- related to
-
SERVER-52618 Sparse hash index should not be used for equality to null match
- Closed