Currently don't check ReadConcern in a transaction for aggregate command

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.2.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Repl 2021-10-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      If a stage doesn't run for certain read concerns and that stage is run in a transaction, we don't check for whether the readconcern/stage combo is legal. It looks like the check should be here, but is skipped for the aggregate command.

              Assignee:
              Wenbin Zhu
              Reporter:
              Ted Tuckman
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: