Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 23 Feb 2012 14:44:49 +0000 (UTC)
From: "Sylvain Lebresne (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <670884571.9991.1330008289332.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <711111550.14444.1311815470351.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2963) Add a convenient way to reset a
 node's schema
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sylvain Lebresne commented on CASSANDRA-2963:
---------------------------------------------

Yeah but my point is that it clearly don't respect the freeze (it's a 'New Feature' ticket), so at least a comment with that kind of justification *before* committing would be nice, otherwise the freeze will become the far west. Communication and transparency are important.
                
> Add a convenient way to reset a node's schema
> ---------------------------------------------
>
>                 Key: CASSANDRA-2963
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2963
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Brandon Williams
>            Assignee: Yuki Morishita
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1.0
>
>         Attachments: CASSANDRA-2963-v3.patch, cassandra-1.1-2963-v2.txt, cassandra-1.1-2963.txt, system_reset_schema.txt
>
>
> People often encounter a schema disagreement where just one node is out of sync.  To get it back in sync, they shutdown the node, move the Schema* and Migration* files out of the system ks, and then start it back up.  Rather than go through this process, it would be nice if you could just tell the node to reset its schema.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira