createOplogFetchingPipelineForResharding() should filter out applyOps entries for aborted transactions

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Sharding 2021-01-25
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The ReshardingAggTest::VerifyPipelineXXXXAbort() tests are currently failing because the applyOps entries are left behind even though there is an abortTransaction entry at then end of the chain. 

      There is code in the createOplogFetchingPipelineForResharding() function that appears to filter these entries out but it does not seem to be working according to the tests.

            Assignee:
            Max Hirschhorn
            Reporter:
            Alexander Taskov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: