You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2013/09/17 11:33:51 UTC
[jira] [Created] (CASSANDRA-6038) Make the inter-major schema
migration barrier more targeted, and, ideally, non-existent
Aleksey Yeschenko created CASSANDRA-6038:
--------------------------------------------
Summary: 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira