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

Consolidate read concern handling on mongos

    • Sharding

      Currently many of the commands on mongos handle read concern separately, e.g. sometimes through a helper class for parsing like QueryRequest (find) or AggregationRequest (aggregate), or sometimes by passing the BSON from the client through after filtering it (distinct). This makes it tricky to change the read concern in a transaction when picking a new global read timestamp or to upconvert read concern to level snapshot like single replica set transactions do. If the way these commands handle read concern could be consolidated to use a single source of truth, like the operation context decoration used by mongod, then modifying the read concern for a transaction would be much simpler.

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            jack.mulrow@mongodb.com Jack Mulrow
            0 Vote for this issue
            3 Start watching this issue