-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Replication - Failover and Concerns
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Once we remove the afterOpTime read concern, we should refactor the list to use cluster times as the keys, avoiding the footgun of the opTime comparator not being totally ordered.