[CASSANDRA-4017] Unify migrations

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.1.0
• Assignee: Sylvain Lebresne
• Reporter: Jonathan Ellis

Authors

Sylvain Lebresne

Reviewers

Pavel Yaskevich

• Created: 08/Mar/12 07:03
• Updated: 16/Apr/19 09:32
• Resolved: 18/Mar/12 10:18

Description

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.