[SERVER-29729] remove afterOpTime readConcern argument Created: 19/Jun/17  Updated: 12/Dec/23

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: Backlog - Catalog and Routing
Resolution: Unresolved Votes: 0
Labels: 12/12
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-44097 Remove term from config server opTime... Closed
depends on SERVER-50675 Get rid of Grid's configOpTime after ... Closed
Assigned Teams:
Catalog and Routing
Participants:
Story Points: 2

 Description   

Currently there could be afterClusterTime and afterOpTime arguments.
Those arguments can be merged.
While afterOpTime uses an opTime , the "term" argument is not used as the afterOpTime reads are always with level = majority.



 Comments   
Comment by Spencer Brody (Inactive) [ 26/Mar/18 ]

Can I put a plug in for this ticket? There's a lot of code duplication and developer confusion in this area that could be eliminated if this work was done.
kaloian.manassiev

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