cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6038) Make the inter-major schema migration barrier more targeted, and, ideally, non-existent
Date Fri, 10 Jan 2014 20:57:50 GMT

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

Jonathan Ellis commented on CASSANDRA-6038:
-------------------------------------------

So if I have a 2.1 node in my 2.0 cluster, as of right now I can't propagate changes from
2.1 -> 2.0 but at least it won't log scary things?

> Make the inter-major schema migration barrier more targeted, and, ideally, non-existent
> ---------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-6038
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6038
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Aleksey Yeschenko
>             Fix For: 2.1
>
>
> CASSANDRA-5845 made it so that schema changes in a major-mixed cluster are not propagated
to the minorer-major nodes. This lets us perform backwards-incompatible schema changes in
major releases safely - like adding the schema_triggers table, moving all the aliases to schema_columns,
getting rid of the deprecated schema columns, etc.
> Even this limitation might be too strict, however, and should be avoided if possible
(starting with at least versioning schema separately from messaging service versioning, and
resorting to major->minor schema block only when truly necessary and not for every x->y
pair). 



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

Mime
View raw message