[SERVER-27161] Change places where we compare Timestamps to comparing OpTimes instead Created: 22/Nov/16  Updated: 27/Oct/17  Resolved: 27/Oct/17

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

Type: Task Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-27099 Consider removing comparison operator... Closed
Sprint: Repl 2017-01-23
Participants:

 Description   

Almost everywhere that compares Timestamps should probably be comparing OpTimes instead. Even when it's technically correct to compare timestamps, so long as it's also correct to compare optimes and doing so won't break conversions between pv0 and pv1, we should always default to comparing optimes so that every place that compares Timestamps is viewed as suspicious.



 Comments   
Comment by Spencer Brody (Inactive) [ 27/Oct/17 ]

We'll do this as it comes up, rather than making a single push to do it.

Comment by Spencer Brody (Inactive) [ 16/Dec/16 ]

We shouldn't do this until we've considered SERVER-27099 and decided on what we want to do about optime comparisons in general

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