Skip to content
This repository has been archived by the owner on Jul 22, 2020. It is now read-only.

Capability to specify the names of "cassandra_migration_version*" tables #16

Closed
james-hu opened this issue Sep 28, 2016 · 2 comments
Closed

Comments

@james-hu
Copy link
Contributor

Outcome Desired

Be able to specify the names of "cassandra_migration_version*" tables in KeyspaceConfiguration or CassandraMigration

  • Table name prefix or suffix or full name can be specified
  • This allows multiple independent applications or modules share the same keyspace while all using cassandra-migration without interfering with each other

## Definition of Done

Table name prefix or suffix or full name can be specified in KeyspaceConfiguration or CassandraMigration, therefore,

  • Multiple migrations can be tracked in the same keyspace.

## Out of Scope
## How to Demo 1. Do migration with some .cql files on a keyspace 2. Do another independent migration with some other .cql files and different names of "cassandra_migration_version*" tables on the same keyspace 3. Check to confirm both migrations succeeded.
@james-hu james-hu changed the title capability to specify the name of "cassandra_migration_version*" table Capability to specify the names of "cassandra_migration_version*" tables Sep 28, 2016
@james-hu
Copy link
Contributor Author

Just wrote my first lines of Kotlin code, and created a pull request :-)

@hhandoko
Copy link
Owner

Thanks @james-hu 👍 I've reviewed and merged the PR.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants