[
https://issues.apache.org/jira/browse/CASSANDRA-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231021#comment-13231021
]
Sylvain Lebresne commented on CASSANDRA-4017:
---------------------------------------------
bq. We could do something similar as a one-off for MoveTest
Good idea. I've push 2 new commits to my github branch
(https://github.com/pcmanus/cassandra/commits/4017). The first one fixes the
unit tests using the idea above. The second one is just a small bug fix of the
previous patch. I've checked that with all this, both unit and system tests are
passing (and the cql3 tests I have).
> 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
