[
https://issues.apache.org/jira/browse/CASSANDRA-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-15848:
----------------------------------------
Test and Documentation Plan: Added unit test. Existing unit/dtest/in-jvm
dtests run.
Status: Patch Available (was: Open)
||branch||utests||in-jvm dtests||dtests_with_vnodes||dtests_no_vnodes||
|[15848-trunk|https://github.com/beobal/cassandra/tree/15848-trunk]|[jdk8|https://circleci.com/gh/beobal/cassandra/1460],
[jdk11|https://circleci.com/gh/beobal/cassandra/1461]|[jdk8|https://circleci.com/gh/beobal/cassandra/1459],
[jdk11|https://circleci.com/gh/beobal/cassandra/1458]|[jdk8|https://circleci.com/gh/beobal/cassandra/1462],
[jdk11|https://circleci.com/gh/beobal/cassandra/1465]|[jdk8|https://circleci.com/gh/beobal/cassandra/1463],
[jdk11|https://circleci.com/gh/beobal/cassandra/1464]|
> 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: [email protected]
For additional commands, e-mail: [email protected]
