geoNear command doesn't handle versioning correctly

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Duplicate
    • Priority: Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Geo, Sharding
    • None
    • Sharding
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      geoNear command doesn't handle versioning correctly, so it will return duplicated or missing results if there is a concurrent chunk migration (or a shard has orphaned documents).

              Assignee:
              [DO NOT USE] Backlog - Sharding Team
              Reporter:
              Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: