[SERVER-18880] GeoMatchExpression::equivalent and GeoNearMatchExpression::equivalent should check for equivalence in their respective GeoExpression and GeoNearExpression Created: 08/Jun/15  Updated: 15/Jun/15  Resolved: 15/Jun/15

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: Needs Triage
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Qingyang Chen Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16912 Complete the implementation of GeoMat... Closed
Participants:

 Description   

GeoMatchExpression::equivalent and GeoNearMatchExpression::equivalent currently compares the raw BSON objects (_rawObj), which does not equate to fully-correct equivalence between the match expressions. We should implement equivalence in the fully-correct sense that the GeoExpression and GeoNearExpression (_query) are checked for full equivalence as well.



 Comments   
Comment by David Storch [ 15/Jun/15 ]

Checking equivalence of geo MatchExpressions is already implemented by comparing the raw BSON of the geo predicate (see SERVER-16912). Since this is only used for testing, we are not currently planning to change the implementation to use parsed representations of the geo filter (i.e. a "geo-aware" implementation).

Generated at Thu Feb 08 03:49:01 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.