If non-geo fields are not multikey index, we can intersect bounds over non-geo field of compound geo index. Although geo index generates more than one geohash index key for a document, geo index is not "multikey" in terms of query planning, because the predicate of geo field is limited to the same semantic of "$elemMatch", i.e. whether any geohash key of a document is in these intervals. Thus, it's possible to intersect bounds over non-geo field of compound geo index, if they are not "multikey".
- duplicates
-
SERVER-4468 Keep track of multi-key fields in index
-
- Closed
-
- is duplicated by
-
SERVER-14264 Compound index on 2dsphere and datetime very slow in 2.6.1 and different result than in 2.4.10
-
- Closed
-