cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4381) Add an initial_schema option
Date Wed, 27 Jun 2012 15:40:44 GMT


Brandon Williams commented on CASSANDRA-4381:

Given CASSANDRA-2963, do we really need this?  In particular typing in a uuid sounds error
prone and tedious vs resetting the 'bad' node.
> Add an initial_schema option
> ----------------------------
>                 Key: CASSANDRA-4381
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>    Affects Versions: 1.0.0
>            Reporter: Joaquin Casares
>            Priority: Minor
>              Labels: lhf
>             Fix For: 1.1.2
> Just like the initial_token option, we can have an option that lists the initial schema
we want a node to read.
> This comes in handy in situations where multiple nodes have schema disagreements, even
if split between 2 or more schemas.
> This can be a hidden option, but would be nice to see in rare cases, especially since
I've been noticing that schema disagreement resolution has been taking more than one round
of restarts lately.

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