Also be aware of https://issues.apache.org/jira/browse/CASSANDRA-7734 if you
are using C* 2.0.6+ (2.0.6 introduced a change that can sometimes causes
initial schema propagation not to happen, introducing potentially long delays
until some other code path repairs it later)
On Sep 30, 2014, at 1:
The system.peers table which is a copy of some gossip info the node has
stored, including the schema version. You should query this and wait until
all schema versions have converged.
http://www.datastax.com/documentation/cql/3.0/cql/cql_using/use_sys_tab_cluster_t.html
http://www.datastax.com/dev
Hi all,
I often have problems with code that I write that uses the DataStax Java
driver to create / modify a keyspace or table and then soon after reads the
metadata for the keyspace to verify that whatever changes I made the
keyspace or table are complete.
As an example, I may create a table cal
