Hello Mark
Second, any ideas what could be creating bottlenecks for schema alteration?
I am not too sure what could be going on to make things that long, but
about the corrupted data, I've seen it before. Here are some thoughts
around schema changes and finding the bottlenecks:
Ideally, use co
I am doing post-mortem on an issue with our cassandra cluster. One of our
tables became corrupt and had to be restored via a backup. The table
schema has been undergoing active development, so the number of "alter
table" statements was quite large (300+). Currently, we use cqlsh to do
schema loa
