There is a known issue for concurrent schema migrations
https://issues.apache.org/jira/browse/CASSANDRA-1391
Once they diverge the I think you can delete the schema by removing the
necessary system files and leaving the data files in place, then re-creating
the files.
And yes, you should not
Thanks for the quick response!. I will reconsider the schema.
However, the problem troubles me somehow. How are schema changes supposed to
be done? Should I serialize them, should I halt other cluster operations
while I do the schema change? Is this a known problem with cassandra?
The other quest
Uh... don't create a column family per user. Column families are meant to be
fairly static; conceptually equivalent to a table in a relational database.
Why do you need (or even want) a CF per user? Reconsider your data model, a
single column family with an inverted index for a 'user' column is pro
