Because allPaths indexes are effectively a collection of single-field indexes on each field of the document, the planner generates a number of AND_SORTED plans for queries involving two or more of the indexed fields. While this is consistent with the planner's behaviour in the case where each individual field was indexed separately, we should consider banning the planner from generating these plans for an allPaths index.