Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-18476

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

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Querying
    • Query Execution

    Description

      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.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4975 covered index projection may be improperly applied after index becomes multikey during yield

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-17678 IndexScan doesn't dedup if index becomes multikey during query execution

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-41058 Add concurrency workload targeted at multikey index writes

          • Major - P3 - Major loss of function.
          • Backlog

          Activity

            People

              backlog-query-execution Backlog - Query Execution
              dan@mongodb.com Daniel Pasette (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              15 Start watching this issue

              Dates

                Created:
                Updated: