Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-51431

BF Day: Transaction read concerns are not honored by mongo shell

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc0
    • Component/s: Shell
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.9
    • Sprint:
      STM 2021-03-22, STM 2021-04-05
    • Linked BF Score:
      129
    • Story Points:
      2

      Description

      The mongo shell doesn't seem to honor the following statement from the documentation: "If the transaction-level read concern is unset, the transaction-level read concern defaults to the session-level read concern."

      An operation is always executed with the session-level read concern (if set) while the eventual transaction read-level concern - set on the session when starting a new transaction - is completely ignored.

      It should be adopted a solution similar to the one implemented by nodejs driver that is assigning a read-concern to an operation respecting the correct order (transaction RC || session RC || client RC).

        Attachments

          Activity

            People

            Assignee:
            carl.worley Raiden Worley
            Reporter:
            pierlauro.sciarelli Pierlauro Sciarelli
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: