[ https://issues.apache.org/jira/browse/CASSANDRA-15848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sam Tunnicliffe updated CASSANDRA-15848: ---------------------------------------- Bug Category: Parent values: Availability(12983)Level 1 values: Response Crash(12991) Complexity: Low Hanging Fruit Discovered By: User Report Fix Version/s: 4.0-alpha Severity: Normal Status: Open (was: Triage Needed) > 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-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org