Investigate PathArraynessChecker not firing for in-memory storage engine mongod

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.1.0-rc0, 9.0.0-rc3
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • ALL
    • v9.0
    • Hide

      Ensure you have at least the commit from SERVER-127609 in your branch.

      Run:

      buildscripts/resmoke.py run --suite=no_passthrough_with_mongod --storageEngine=inMemory -- jstests/noPassthroughWithMongod/query/join/yield_then_update_to_multi_key_index_large_join.js

      The test fails

      Show
      Ensure you have at least the commit from SERVER-127609 in your branch. Run: buildscripts/resmoke.py run --suite=no_passthrough_with_mongod --storageEngine=inMemory -- jstests/noPassthroughWithMongod/query/join/yield_then_update_to_multi_key_index_large_join.js The test fails
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-127609 updated yield_then_update_to_multi_key_index.js and yield_then_update_to_multi_key_index_large_join.js to expect query being killed if a join field becomes an array in between a yield/restore (which is achieved by using batchSize: 1 and getMore() in these tests).

      Interestingly, while yield_then_update_to_multi_key_index.js test passes on all variants, yield_then_update_to_multi_key_index_large_join.js fails on the in-memory variant on evergreen because the query does not get killed.

      We should investigate why this discrepancy exists in case there is an underlying bug.

            Assignee:
            Matt Boros
            Reporter:
            Naafiyan Ahmed
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: