[SERVER-20334] New mongos read path must forward readConcern to the shards Created: 09/Sep/15  Updated: 07/Oct/15  Resolved: 18/Sep/15

Status: Closed
Project: Core Server
Component/s: Querying, Sharding
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: David Storch Assignee: YunHe Wang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Quint 9 09/18/15
Participants:

 Description   

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



 Comments   
Comment by Githook User [ 18/Sep/15 ]

Author:

{u'username': u'yhjw88', u'name': u'Yunhe (John) Wang', u'email': u'yunhe.wang@mongodb.com'}

Message: SERVER-20334 Added readConcern forwarding to mongos find
Branch: master
https://github.com/mongodb/mongo/commit/79baef75f04ab381eaf9805343f15483ec4edcde

Generated at Thu Feb 08 03:53:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.