You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2020/06/04 08:18:00 UTC
[jira] [Comment Edited] (CASSANDRA-15848) Fully purged static row
causes NPE in repaired data tracking
[ https://issues.apache.org/jira/browse/CASSANDRA-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125672#comment-17125672 ]
Marcus Eriksson edited comment on CASSANDRA-15848 at 6/4/20, 8:17 AM:
----------------------------------------------------------------------
+1
was (Author: krummas):
+1 if tests look good
> Fully purged static row causes NPE in repaired data tracking
> ------------------------------------------------------------
>
> Key: CASSANDRA-15848
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15848
> Project: Cassandra
> Issue Type: Bug
> Components: Legacy/Local Write-Read Paths
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 4.0-alpha
>
>
> During repaired data tracking, if the result of applying the purge function to a static row is null, an exception is thrown from RepairedDataInfo. This will cause a read exception from the replica and could lead to unavailable results if hit on multiple replicas. A workaround is to disable repaired data tracking.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org