> Once you run incremental repair, your data is permanently marked as repaired
This is also the case for full repairs, if I'm not mistaken. I'll admit I'm not as familiar with the quirks of repair in 2.2, but prior to 4.0/CASSANDRA-9143, any global repair ends with an anticompaction that marks sstables as repaired. Looking at the RepairRunnable class, this does seem to be the case. Assuming I'm not missing something here, that should mean that he shouldn't need to mark sstables as unrepaired?
