[SERVER-47575] Support snapshot reads across getMores Created: 15/Apr/20  Updated: 29/Oct/23  Resolved: 27/Apr/20

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

Type: Task Priority: Major - P3
Reporter: Lingzhi Deng Assignee: A. Jesse Jiryu Davis
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-47573 Update readConcern to include the atC... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2020-05-04
Participants:

 Description   

Change applyCursorReadConcern to handle “atClusterTime” and call setTimestampReadSource with kProvided and pass the timestamp selected as “atClusterTime”.



 Comments   
Comment by A. Jesse Jiryu Davis [ 27/Apr/20 ]

Changing readConcern from client side is indeed prohibited, see getmore_cmd.cpp.

Comment by A. Jesse Jiryu Davis [ 27/Apr/20 ]

Fixed in the same commit as SERVER-47572 and SERVER-47573:

https://github.com/mongodb/mongo/commit/2f7abf486d3fc0f785cef1df949ae7fb80c8ba58

Comment by A. Jesse Jiryu Davis [ 21/Apr/20 ]

This was largely implemented in SERVER-47573. Verify that any attempt to change the readConcern from the client side is prohibited. Think of other tests we lack.

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