[SERVER-83278] Update snapshot read's returned operationTime to be the timestamp of the snapshot Created: 15/Nov/23  Updated: 05/Feb/24

Status: In Progress
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Huayu Ouyang Assignee: Wenqin Ye
Resolution: Unresolved Votes: 1
Labels: cs-subteam3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Cluster Scalability
Sprint: Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19
Participants:
Story Points: 2

 Description   

Based on this code, when we return the operation time of a read operation, if the read concern was majority, we return the CurrentCommittedSnapshotOpTime, while if the read concern was anything else (local, linearizable, or snapshot), we returned the lastApplied optime.

For snapshot reads, is this the intended behavior/contract for operationTIme?
We do additionally attach an atClusterTime field in cursor responses. Should the operationTime also be the `atClusterTime`, or is it ok to keep it as the lastApplied?


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