When a query contains multiple predicates on the same field where some are sparse index compatible and others are not, the query planner performs a issues a collection scan plan instead of an index scan plan on the sparse index for the compatible predicates and applying incompatible predicates as filters.

This is caused by incorrect overriding of the sparse index compatibility info in QueryPlannerIXSelect::getFields The fix is never override supportSparse = true by supportSparse = False.