cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-4017) Unify migrations
Date Sun, 18 Mar 2012 10:20:39 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sylvain Lebresne resolved CASSANDRA-4017.
-----------------------------------------

    Resolution: Fixed

Committed, thanks
                
> Unify migrations
> ----------------
>
>                 Key: CASSANDRA-4017
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4017
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>             Fix For: 1.1.0
>
>
> Now that we can send a schema as a RowMutation, there's no need to keep separate add/drop/update
migration classes around.  Let's just send the schema to our counterparts and let them figure
out what changed.  Currently we have "figure out what changed" code to both generate migrations
on the sender, and for application on the target, which adds complexity.

--
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

        

Mime
View raw message