You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Blake Eggleston (JIRA)" <ji...@apache.org> on 2017/04/10 17:54:41 UTC

[jira] [Created] (CASSANDRA-13430) Cleanup isIncremental/repairedAt usage

Blake Eggleston created CASSANDRA-13430:
-------------------------------------------

             Summary: Cleanup isIncremental/repairedAt usage
                 Key: CASSANDRA-13430
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13430
             Project: Cassandra
          Issue Type: Improvement
            Reporter: Blake Eggleston
            Assignee: Blake Eggleston


Post CASSANDRA-9143, there's no longer a reason to pass around {{isIncremental}} or {{repairedAt}} in streaming sessions, as well as some places in repair. The {{pendingRepair}} & {{repairedAt}} values should only be set at the beginning/finalize stages of incremental repair and just follow sstables around as they're streamed. Keeping these values with sstables also fixes an edge case where you could leak repaired data back into unrepaired if you run full and incremental repairs concurrently.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)