You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Remove read-after-write/monotonic reads for 2.12.
> Although the design (read-after-write/monotonic reads/linearizable)
gives a lot of control and flexibility, we'll need to decide whether
this adds a bunch of complexity which would be (too) hard to understand
by an end-user, in which case we might need to revisit this.
#7146 (comment)
The current design is very flexible, but adds a ton of complexity that
needs to be handled on a per-request basis. We've discussed whether this
should instead be on a per-stream basis. Where on a replicated
stream/KV/ObjectStore the reads are serializable by default, but one can
opt-in to linearizable for that whole stream. That would mean client
code doesn't need to change at all to get this guarantee, only the
stream setting would need to be updated.
We'll need to discuss this further, and likely introduce this early in
the next 2.14 (skipping 2.13) release cycle.
Relates to #6557
Relates to PRs: #6970,
#7146
Signed-off-by: Maurice van Veen <[email protected]>
0 commit comments