[ https://issues.apache.org/jira/browse/CASSANDRA-15977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202250#comment-17202250 ]
Andres de la Peña commented on CASSANDRA-15977: ----------------------------------------------- I've added a [PR for 3.11|https://github.com/apache/cassandra/pull/758] with only the bug fix mentioned above. 3.0 is not affected because, if I'm right, it's intended to repair entire rows (see CASSANDRA-10655 and CASSANDRA-10657). [~maedhroz] I understand that the dtests created here under the {{40_Quality_Test}} epic are only for 4.0 and shouldn't be backported to previous branches, is that correct? > 4.0 quality testing: Read Repair > -------------------------------- > > Key: CASSANDRA-15977 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15977 > Project: Cassandra > Issue Type: Task > Components: Test/dtest/java, Test/unit > Reporter: Andres de la Peña > Assignee: Andres de la Peña > Priority: Normal > Fix For: 4.0-beta > > Time Spent: 13h 20m > Remaining Estimate: 0h > > This is a subtask of CASSANDRA-15579 focusing on read repair. > [This > document|https://docs.google.com/document/d/1-gldHcdLSMRbDhhI8ahs_tPeAZsjurjXr38xABVjWHE/edit?usp=sharing] > lists and describes the existing functional tests for read repair, so we can > have a broad view of what is currently covered. We can comment on this > document and add ideas for new cases/tests, so it can gradually evolve to a > more or less detailed test plan. -- 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