[
https://issues.apache.org/jira/browse/CASSANDRA-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730771#comment-13730771
]
Jason Brown commented on CASSANDRA-5839:
----------------------------------------
I think it should be replicated for ease of use, as I believe this feature is
an ease of use concern (for admins) so they don't have to rummage around in
distributed log files.
Other items to capture might include the coordinator's hostname (I think we
used to call that node the 'initiator' back in the day) and the set of the
endpoints participating in the repair (possibly with datacenter).
> 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: Jason Brown
> Priority: Minor
> Fix For: 2.0.1
>
>
> As noted in CASSANDRA-2405, it would be useful to store repair results,
> particularly with sub-range repair available (CASSANDRA-5280).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
