-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Affects Version/s: None
-
Component/s: Retryability
-
None
-
None
-
Ruby Drivers
-
None
-
None
-
None
-
None
-
None
-
None
The "modern" retryable reads implementation was finished in April 2019, and retryable writes is from 2017. Do we still need to support the legacy retry implementations? I understand that there are some operations that may not be supported by the modern retry spec, which were supported under the legacy implementation, so even if we need to keep the implementation, can we deprecate and remove the options for people to select the legacy implementation? (:retry_reads and :retry_writes).
