[
https://issues.apache.org/jira/browse/CASSANDRA-15019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793030#comment-16793030
]
Jordan West commented on CASSANDRA-15019:
-----------------------------------------
[~beobal] also shouldn't
[this|https://github.com/beobal/cassandra/commit/c92b9dea14e128f2063dca01526c3afcd5559d51#diff-71f06c193f5b5e270cf8ac695164f43aR2052]
call be to {{DatabaseDescriptor.getRepairedDataTrackingForRangeReadsEnabled}}.
Just noticing this now. It existed before the patch.
> 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
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
