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

Mongos should not upconvert transaction read concern level to snapshot if none is provided

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • Sharding 2019-02-11

    Description

      If a user starts a transaction without specifying a read concern level, mongos currently upconverts the level to "snapshot." Instead, mongos should allow an empty read concern level.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-39672 ReadConcern level in multi-statement transactions defaults to "snapshot"

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. DOCS-11944 Docs for SERVER-36240: Make transactions on mongos use snapshot level readConcern if no level was provided

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              jack.mulrow@mongodb.com Jack Mulrow
              jack.mulrow@mongodb.com Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: