-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
-
0
Instead of explicitly stating that $geoNear on a view is disallowed, the assertion reads
"$geoNear was not the first stage in the pipeline after optimization. Is optimization disabled or inhibited?"
which is true given that the view gets placed in front of the $geoNear, but this could be confusing to the user. We should instead log that it can't be used against a view.