Cassandra - Schema Versioning
As changes are made to the cassandra schema, the ability to version changes are needed.
For Example, a new column family is introduced, or a new column is added to an existing column family.
On startup of poppy, the cassandra driver currently creates a new key space if it does not already exist.
This change should do the following:
- Query the current version of schema running in cassandra
- Replay the schema changes (CREATE, DELETE, statements) from the current schema version to the latest schema version.
- The cassandra schema file should contain version blocks for each version change of the schema
- Cassandra will need a new column family to store the current schema version.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- Amit Gandhi
- Direction:
- Approved
- Assignee:
- Tony Tan
- Definition:
- Approved
- Series goal:
- Accepted for kilo
- Implementation:
- Implemented
- Milestone target:
- kilo-3
- Started by
- Amit Gandhi
- Completed by
- Amit Gandhi
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Add cassandra schema migration framework Implements: blueprint cassandra-