[SERVER-30463] add support for readConcern to explain Created: 01/Aug/17  Updated: 26/Apr/19  Resolved: 10/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Misha Tyulenev
Resolution: Duplicate Votes: 0
Labels: PM-221
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-29987 Make all non-write operations take re... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-08-21
Participants:

 Description   

Its a particular case of SERVER-29987. As a result the scenario

coll.createIndex({x:1});
coll.explain().find({x:1 });

will may not the use the index if the explain goes to the secondary
Enabling support for readConcern will make the explain command wait for the clusterTime of the createIndex result and hence will be able to see the updated schema.



 Comments   
Comment by Ian Whalen (Inactive) [ 26/Apr/19 ]

Switching "Drivers Changes Needed" from "Maybe" to "Not Needed" since this was closed as something other than Fixed.

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