[SERVER-33855] Validate that readConcern with inconsistent atClusterTime fails Created: 13/Mar/18  Updated: 06/Dec/22  Resolved: 10/Apr/18

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: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

Validate that readConcern can have atClusterTime only if level is "snapshot" (may be already validated)



 Comments   
Comment by Misha Tyulenev [ 10/Apr/18 ]

The fix is in jstests/noPassthrough/readConcern_atClusterTime.js

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