-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 3.4.9
-
Component/s: Aggregation Framework, Geo
-
None
-
Fully Compatible
-
ALL
-
-
Query 2017-11-13
We have upgraded MongoDB 3.2 to 3.4, but have not yet setFeatureCompatibilityVersion to 3.4
When trying to use aggregate $geoNear, it fails with an error. Using find $nearSphere succeeds with no error.
If I set setFeatureCompatibilityVersion to "3.4", the aggregate succeeds, but it shouldn't have failed when set to "3.2" as I wasn't trying to do anything with collation at all, and it is still a v:1 index. Interestingly, if I go up to setFeatureCompatibilityVersion "3.4", create a v:2 / 2dsphereIndexVersion:3 index, then setFeatureCompatibilityVersion back to "3.2", it's the same exact error, so I don't actually think it has anything to do with the index v:1 vs v:2 at all, just some bug in the aggregation framework perhaps?