Investigate test failure in documentKey when match expression optimization is disabled on full cluster

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When match expression optimization is disabled on whole cluster by adding the code:
       

      FixtureHelpers.runCommandOnEachPrimary({ db:db.getSiblingDB("admin"), cmdObj: {configureFailPoint:"disableMatchExpressionOptimization", mode:"alwaysOn"} });

       
       

      A failure is seen in the following line where returned document at oplog seems to be 1 but expected is 2.

      https://github.com/mongodb/mongo/blob/92738c5fa0e8169299e5393e88159b8cbb9559ca/jstests/change_streams/oplog_rewrite/change_stream_match_pushdown_documentKey_rewrite.js#L149

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

              Created:
              Updated:
              Resolved: