In-progress queries may return incorrect results if an index concurrently becomes multikey

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Query Execution
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Query planning logic depends substantially on whether or not the set of available indices is multikey, and on which indexed paths are multikey. If this information changes due to a concurrent update or insert creating a new array path, in progress queries may be using a plan that is now invalid. One way to fix this would be to kill all in-progress queries for a particular collection when making a change to that collection's multikeyness metadata.

              Assignee:
              [DO NOT USE] Backlog - Query Execution
              Reporter:
              Daniel Pasette (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              17 Start watching this issue

                Created:
                Updated: