[SERVER-32266] Test readConcern level:snapshot on mongos Created: 11/Dec/17  Updated: 06/Dec/22  Resolved: 20/Mar/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

Issue Links:
Duplicate
duplicates SERVER-33061 Validate level:snapshot Closed
Assigned Teams:
Sharding
Sprint: Sharding 2018-04-09
Participants:

 Description   

readConcern:

{level:snapshot}

parsing has been already added to ReadConcernArgs,
1. To src/mongo/s/strategy.cpp
add code that verifies that level:snapshot is set in a command that is a part of at transaction.
if not must return

ErrorCodes::InvalidOptions

error

2. add a testcase to sharding suite that verifies that
a) level:snapshot can be parsed by mongos
b) level:snapshot is only allowed when there is a txnNumber and lsid - i.e its allowed only as a part of a transaction
c) level:snapshot is permitted only for the find, aggregate, count, distinct commands. - this is not going to be checked on mongos but is verified on mongod with a supportsReadConcern call

There are geoNear, group, geoSearch and parallelCollectionScan commands that may support it as well if it will be free but its not required.


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