Cassandra - Schema Versioning

Registered by Amit Gandhi

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:
milestone icon kilo-3
Started by
Amit Gandhi
Completed by
Amit Gandhi

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/cassandra-schema-versioning,n,z

Addressed by: https://review.openstack.org/159605
    Add cassandra schema migration framework Implements: blueprint cassandra-schema-versioning

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.