When using cassandra storage type, automatically generate requested keyspace if it doesn't exist. about cassandra-reaper HOT 3 CLOSED

I had the same idea when adding automatic schema migration in the codebase, and thought we should create the keyspace automatically.

I concluded that this was not a good idea for a couple reasons :

• ops need to set the replication strategy explicitly to avoid consistency issues as Reaper uses LOCAL_QUORUM by default (and that's overall a C* best practice, especially as we do not own the clusters that Reaper will get installed on)
• Technically, this would require to hack the way dropwizard-cassandra works in order to create a keyspace with our arbitrary number of replicas. Currently, I found now way to do this properly unless I created multiple connections to the cluster.

Given that the benefits are really up to debate, I'd rather not add hacky stuff in the code to perform the KS creation.

from cassandra-reaper.

Given that the benefits are really up to debate, I'd rather not add hacky stuff in the code to perform the KS creation.

Agreed.
This works with in-house code where you can, through environment profiles in the configuration, define the keyspace RF per environment.
In open source we don't know what the RF should be for a user, and should just leave keyspace creation logic alone.

from cassandra-reaper.

Sounds arguments against. I'll go ahead and close this.

from cassandra-reaper.