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

Sam Tunnicliffe commented on CASSANDRA-15019:
---------------------------------------------

|[trunk|https://github.com/beobal/cassandra/tree/15019-trunk]|[dtest 
PR|https://github.com/apache/cassandra-dtest/pull/43]|[CI (with patched dtest 
branch)|https://circleci.com/workflow-run/8dec0886-5b8d-48e3-a4a9-c35723582aeb]|


> 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: Major
>             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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to