> 1. Can this schema version issue happen in newer versions of Cassandra (>1.0)
> ?
AFAIK yes. Schema changes are assumed to happen infrequently, and to only be
started if the cluster is in schema agreement. Clients (include the CLI and
CQL) take care of this.
> 2. When the node is UP and we d
Thanks Aaron.
This is great. A couple of questions if you don't mind...
1. Can this schema version issue happen in newer versions of Cassandra
(>1.0) ?
2. When the node is UP and we do this, even though logs errors, still would
everything come back to normal just like we shut down and delete and
Go to one of the nodes, stop it and delete the Migrations and Schema files in
the system keyspace.
When you restart the node it will stream the migrations the other. Note that if
the node is UP and accepting traffic it may log errors about missing CF's
during this time.
Cheers
---
Hi,
I try to add column families programatically and end up with 2 schema
versions in the Cassandra cluster. Using Cassandra 0.7.
Is there a way to bring this back to normal (to one schema version) through
the cli or through the API?
--
Regards,
Tharindu
blog: http://mackiemathew.com/
