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

New mongos read path must forward readConcern to the shards

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.9
    • Affects Version/s: None
    • Component/s: Querying, Sharding
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Quint 9 09/18/15

      Right now the read concern is stripped out when the query received from the client is transformed into a query suitable for delivering to the shards.

      Fails the following jstest:
      python buildscripts/resmoke.py --executor=sharding_jscore_passthrough jstests/core/read_after_optime.js

            Assignee:
            yunhe.wang YunHe Wang
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: