You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2019/05/31 17:15:00 UTC
[jira] [Updated] (CASSANDRA-15019) Repaired data tracking isn't
working for range queries
[ https://issues.apache.org/jira/browse/CASSANDRA-15019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-15019:
-------------------------------------
Status: Open (was: Resolved)
> Repaired data tracking isn't working for range queries
> ------------------------------------------------------
>
> Key: CASSANDRA-15019
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15019
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination, Consistency/Repair, Test/dtest
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Normal
> Fix For: 4.0
>
> Attachments: RepairDigestTrackingTest.java
>
>
> CASSANDRA-14145 introduced optional tracking of the repaired dataset used to construct a read response. If enabled, each replica computes a digest for the repaired portion of the data, which the coordinator compares in order to detect divergence between replicas. This isn't working correctly for range reads, as the ReadCommand instance that the DataResolver is intialized with does not have the tracking flag set. This has been undetected up until now as the dtest which should verify it also has a bug in that when the relevant range query is issued the test expectations are being incorrectly set.
--
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