Closed kevinpotgieter closed 8 years ago
which queries are you thinking about? I assume most queries people manage with cqlmigrate will be schema altering ones that pay no attention to consistency
I was thinking more along the lines of addressing the inserts into the schema_updates
table which probably doesn't require ALL, and allowing the user to specify EACH_QUORUM for writes and LOCAL_QUORUM for reads still achieves the same result, but without requiring the high availability of all the nodes. Of course this could be applied to not only the schema_updates
table, but for any other non-DDL changes you execute as part of your migration.
FYI - I believe this has already been included as part of 0.9.4 release
When running CqlMigrate, allow the user to provide configuration to allow them to override the consistency levels for reads and writes to whatever they deem to be appropriate for their context. Currently the CL defaults are LOCAL_ONE and ALL for reads and writes respectively.