query optimizer cursor may return partial result set for a $or query if the last index match for a $or clause is deleted while it is "current"

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.0.3, 2.1.0
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is a concurrency issue where the cursor will finish instead of advancing from one $or clause to the next if a particular race condition occurs. This currently affects distinct, group, map/reduce etc which rely on the query optimizer cursor.

      Test and fix are ready to go if you assign a version.

              Assignee:
              Aaron Staple (Inactive)
              Reporter:
              Aaron Staple (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: