-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Geo
-
Query Integration
-
ALL
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When using the $geoNear aggregation stage with mismatched coordinate dimensions (3D queries against 2D data or vice versa), the system exhibits behavior that may be misleading. Specifically, when 3D coordinates are provided in the near parameter while querying against 2D coordinate data, the server silently ignores the third coordinate value and processes the query as if a 2D coordinate was provided, without generating any warning or error. Does the $geoNear stage even support working with 3D coordinates?