[
https://issues.apache.org/jira/browse/CASSANDRA-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955402#comment-15955402
]
Blake Eggleston commented on CASSANDRA-13398:
---------------------------------------------
I haven't thought through the implications of modifying the repairedAt value of
sstables, but you're pretty much guaranteed to never get a repaired sstable in
anticompaction in trunk. For that reason, I'd say this shouldn't be applied to
trunk. In fact, there's a bunch of vestigial stuff from the 'old'
anticompaction context that isn't really used anymore and should probably be
removed. I'll factor it out and open a jira when I have some time.
> Skip mutating repairedAt of already repaired sstables
> -----------------------------------------------------
>
> Key: CASSANDRA-13398
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13398
> Project: Cassandra
> Issue Type: Bug
> Reporter: Paulo Motta
> Assignee: Paulo Motta
> Priority: Minor
>
> CASSANDRA-13153 skips anticompaction on sstables already repaired, but we are
> not skipping mutating repairedAt when the sstable is fully contained in the
> repaired range.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
