[
https://issues.apache.org/jira/browse/CASSANDRA-4017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13230596#comment-13230596
]
Jonathan Ellis commented on CASSANDRA-4017:
-------------------------------------------
Maybe we can tackle it from this direction, then:
bq. now that means that SchemaLoader needs to be merged with CleanupHelper
(otherwise, since the cleanup was happening with the schema loading, the
loading was conflicting with the schema of the previous test)
What I did over on CASSANDRA-3967 v2 was to make CleanupHelper manually call
into SchemaLoader explicitly rather than leaving it up to the BeforeClass
annotations as to which runs first.
We could do something similar as a one-off for MoveTest: instead of extending
CleanupHelper and giving up that control, it could call into it manually once
it's set the partitioner the way it wants.
> 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
