[SERVER-16912] Complete the implementation of GeoMatchExpression::equivalent() Created: 16/Jan/15  Updated: 05/Feb/16  Resolved: 10/Jun/15

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

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Qingyang Chen
Resolution: Done Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-18880 GeoMatchExpression::equivalent and Ge... Closed
Backwards Compatibility: Fully Compatible
Sprint: Quint Iteration 5
Participants:

 Description   

MatchExpression subclasses implement the equivalent() virtual method, which take another MatchExpression and return a boolean indicating whether the two expressions represent the same predicate.

The implementation of GeoMatchExpression::equivalent() was never finished (see code here). This can make testing cumbersome, especially in the query planner unit tests as these tests use MatchExpression::equivalent() to verify that the planner is using the correct filters.



 Comments   
Comment by Githook User [ 10/Jun/15 ]

Author:

{u'username': u'coollog', u'name': u'Qingyang Chen', u'email': u'qingyang.chen@10gen.com'}

Message: SERVER-16912 finish implementation of GeoMatchExpression::equivalent().

Closes #982

Signed-off-by: David Storch <david.storch@10gen.com>
Branch: master
https://github.com/mongodb/mongo/commit/8fa3e031acda17e3ec75a2914f6713baeb0d2083

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