[jira] [Commented] (CASSANDRA-15848) Fully purged static row causes NPE in repaired data tracking

["Sam Tunnicliffe (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125670#comment-17125670 ] 

Sam Tunnicliffe commented on CASSANDRA-15848:
---------------------------------------------

Sorry, you're absolutely right, so I've pushed that change.

It looks like Circle has stopped even limited access to job info unless authenticated, but I'll update the CI status when the jobs are finished.

> 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