Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 13 Jan 2014 18:15:25 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12661321.1375416006972.87972.1389636925345@arcas>
In-Reply-To: <JIRA.12661321.1375416006972@arcas>
References: <JIRA.12661321.1375416006972@arcas>
Subject: [jira] [Commented] (CASSANDRA-5839) Save repair data to system
 table
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CASSANDRA-5839?page=3Dcom.atlas=
sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D=
13869781#comment-13869781 ]=20

Jonathan Ellis commented on CASSANDRA-5839:
-------------------------------------------

Not really,  For 5483 we want to know the details of what happened during t=
he repair, not just the end result.

> 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=C3=A5rdell
>            Priority: Minor
>             Fix For: 2.0.5
>
>         Attachments: 2.0.4-5839-draft.patch
>
>
> As noted in CASSANDRA-2405, it would be useful to store repair results, p=
articularly with sub-range repair available (CASSANDRA-5280).


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)