What you describe below sounds like what I want to do. I think that the only
additional thing I am requesting is to export the migrations from the dev
cluster (since Cassandra already has a table that saves them - I just want
that information!) so I can import it to the other clusters. This would
e
Not sure what sort of changes you are making, but this is my approach.
I've always managed database (my sql, sql server whatever) schema as source
code (SQL DDL statements, CLI script etc). It makes it a lot easier to cold
start the system, test changes and see who changed what.
Once you ha
Actually, I want a way to propagate *any* changes from development to
staging to production, but schema changes are the most important.
Could I use 2221 to propagate schema changes by deleting the schema in the
target cluster, doing "show schema" in the source cluster, redirecting to a
file, and r
What sort of schema changes are you making? can you manage them as a CLI
script under source control ?
You may also be interested in CASSANDRA-2221.
Cheers
Aaron
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 12 May 2011, at 20:45,
My use case is like this: I have a development cluster, a staging cluster
and a production cluster. When I finish a set of migrations (i.e. changes)
on the development cluster, I want to apply them to the staging cluster, and
eventually the production cluster. I don't want to do it by hand, because
