-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
Currently cluster time advancement logic is duplicated in several files and is interspersed with other code. To make it clear how cluster time is handled, everything related to it can be organized in a single class.
- is depended on by
-
RUBY-1807 Client side errors should not change transaction state
- Closed
- links to