GeoMatchExpression::equivalent and GeoNearMatchExpression::equivalent should check for equivalence in their respective GeoExpression and GeoNearExpression

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: Needs Triage
    • Component/s: Querying
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Unassigned
            Reporter:
            Qingyang Chen (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: