[
https://issues.apache.org/jira/browse/CASSANDRA-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953503#comment-15953503
]
Paulo Motta commented on CASSANDRA-13398:
-----------------------------------------
Actually you're right this is a not problem per se, but it can cause
{{repairedAt}} fields not consistent across replicas for a given range, since
the same repair session may update {{repairedAt}} on some replicas
(coordinator) while not on others (participants), what can cause some confusion
if we ever start using this field for anything else other than finding out if
an sstable is repaired or not. Not a big deal though, so I'm fine if we
wontfixit.
> 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)
