Transactions shell helpers shouldn't attach readConcern to any operation but the first in a transaction

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.7.4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-04-23
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When running transactions within a causally consistent session in the shell, all operations in the transaction get an afterClusterTime readConcern attached to them, which will cause all operations after the first to error with InvalidOptions since readConcern is only allowed on the first operation in the transaction

              Assignee:
              Pavithra Vetriselvan
              Reporter:
              Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: