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

Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2014/09/12 19:28:34 UTC

[jira] [Commented] (CASSANDRA-7913) Don't try to set repairedAt on old sstables

    [ https://issues.apache.org/jira/browse/CASSANDRA-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131782#comment-14131782 ] 

Brandon Williams commented on CASSANDRA-7913:
---------------------------------------------

Seems like some kind of warning for those would be appropriate, though.

> Don't try to set repairedAt on old sstables
> -------------------------------------------
>
>                 Key: CASSANDRA-7913
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7913
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Marcus Eriksson
>            Assignee: Marcus Eriksson
>            Priority: Minor
>             Fix For: 2.1.1
>
>         Attachments: 0001-dont-try-to-set-repairedAt-on-old-sstables.patch
>
>
> When using the tool sstablerepairedset we don't care if the sstable actually supports having the repairedAt set



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)