[
https://issues.apache.org/jira/browse/CASSANDRA-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953082#comment-15953082
]
Stefan Podkowinski commented on CASSANDRA-13398:
------------------------------------------------
Although I agree with the ticket description, I wonder if we actually have to
do something here. What's the harm in updating repairedAt in this case? Did you
encounter any issues due to the described behaviour, or what is the motivation
for the proposed changes?
> 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
>
> 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)
