[
https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850694#comment-13850694
]
Jimmy Mårdell commented on CASSANDRA-5839:
------------------------------------------
Thanks for your input, it's very helpful! I didn't know about the
default_time_to_live actually among other things (my CQL is very bad, but I
speak thrift almost natively ;) )
I've made the suggested changes (patch coming), but I realize that perhaps the
logging code should be in SystemKeyspace or (more likely) a new "static" class
SystemKeyspaceDistributed. I'm not a fan of so many static methods but I am a
fan of consistency. What do you think?
> Save repair data to system table
> --------------------------------
>
> Key: CASSANDRA-5839
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5839
> Project: Cassandra
> Issue Type: New Feature
> Components: Core, Tools
> Reporter: Jonathan Ellis
> Assignee: Jimmy Mårdell
> Priority: Minor
> Fix For: 2.0.4
>
> Attachments: 2.0.4-5839-draft.patch
>
>
> As noted in CASSANDRA-2405, it would be useful to store repair results,
> particularly with sub-range repair available (CASSANDRA-5280).
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
