cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2963) Add a convenient way to reset a node's schema
Date Thu, 23 Feb 2012 08:47:49 GMT


Sylvain Lebresne commented on CASSANDRA-2963:

Isn't ninja pushing this to 1.1.0 being a bit loose with the definition of a code freeze?
I'm not asking to revert but at least some form of justification for why something tagged
'New Feature' ends up in 1.1.0 way after the freeze would have been nice.
> Add a convenient way to reset a node's schema
> ---------------------------------------------
>                 Key: CASSANDRA-2963
>                 URL:
>             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,
> 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:!default.jspa
For more information on JIRA, see:


View raw message