You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2018/06/12 22:16:00 UTC
[jira] [Commented] (CASSANDRA-14517) Short read protection can
cause partial updates to be read
[ https://issues.apache.org/jira/browse/CASSANDRA-14517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16510311#comment-16510311 ]
Blake Eggleston commented on CASSANDRA-14517:
---------------------------------------------
Not sure there's much that can be done about this that would be reasonable. There might (_might_) be a way to fix this for SRP, but paging has the same issue
> Short read protection can cause partial updates to be read
> ----------------------------------------------------------
>
> Key: CASSANDRA-14517
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14517
> Project: Cassandra
> Issue Type: Bug
> Reporter: Blake Eggleston
> Priority: Major
> Fix For: 4.0
>
>
> If a read is performed in two parts due to short read protection, and the data being read is written to between reads, the coordinator will return a partial update. Specifically, this will occur if a single partition batch updates clustering values on both sides of the SRP break, or if a range tombstone is written that deletes data on both sides of the break. At the coordinator level, this breaks the expectation that updates to a partition are atomic, and that you can’t see partial updates.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org