You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 22, 2020. It is now read-only.
Make it configurable: consistency level for schema version tracking statements
Currently it is hard coded to ALL, making it configurable gives us possibilities to work around some issues (in very sick use cases, I have to admit).
I have a quick implementation here: https://github.com/james-hu/cassandra-migration/pull/1/files
But probably the configuration should be on CassandraMigration rather than on KeyspaceConfiguration. Then we can pass it as an argument to the constructor of SchemaVersionDAO. That change seems to be a little bit structural. So I think I'd better let you take over.
## Definition of Done
Consistency level is configurable from Java (and command line as well?)
## Out of Scope
Consistency level of migrations scripts provided by the users.
## How to Demo
Create a keyspace that can't satisfy the ConsistencyLevel.ALL, and try to make migration success by setting consistency level to QUORUM.
The text was updated successfully, but these errors were encountered:
Thanks for reaching out @smiklosovic , I'm just a bit inundated at work right now. If you could draft a PR it would really help me 😄 Otherwise, I'll try to get to this on my next opportunity.
Make it configurable: consistency level for schema version tracking statements
Currently it is hard coded to ALL, making it configurable gives us possibilities to work around some issues (in very sick use cases, I have to admit).
I have a quick implementation here: https://github.com/james-hu/cassandra-migration/pull/1/files
But probably the configuration should be on CassandraMigration rather than on KeyspaceConfiguration. Then we can pass it as an argument to the constructor of SchemaVersionDAO. That change seems to be a little bit structural. So I think I'd better let you take over.
## Definition of Done
Consistency level is configurable from Java (and command line as well?)
## Out of Scope
Consistency level of migrations scripts provided by the users.
## How to Demo
Create a keyspace that can't satisfy the ConsistencyLevel.ALL, and try to make migration success by setting consistency level to QUORUM.
The text was updated successfully, but these errors were encountered: