[
https://issues.apache.org/jira/browse/CASSANDRA-11440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-11440.
------------------------------------------
Resolution: Won't Fix
There actually is some cases where reading at CL.ONE is fine, as you might not
care about staleness for some queries (or you've committed at ALL). Plus I
don't see any way to implement this in the first place. I'm sure we can improve
documentation on LWT so users know what they are doing, but closing that ticket
in the meantime.
> consider LWT staleness warning when reading LWT back below serial consistency
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-11440
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11440
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Russ Hatch
> Priority: Minor
>
> When reading a recently written LWT at cl.one, there is a potential for
> staleness. Users are encouraged to read LWT values back at SERIAL consistency
> level for events to remain linearizable.
> If there's a low-impact way to warn about staleness, this could prevent
> people from shooting themselves in the foot.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
