Tommy Stendahl created CASSJAVA-69:
--------------------------------------
Summary: Schema agreement check after DDL query is unreliable
Key: CASSJAVA-69
URL: https://issues.apache.org/jira/browse/CASSJAVA-69
Project: Apache Cassandra Java driver
Issue Type: Bug
Components: Core
Reporter: Tommy Stendahl
Version 4.x of the java-driver always do the schema agreement check after a DDL
query on the control connection. This can be unreliable if DDL query was done
on another node since the node with the control connection might not be
immediately aware of the schema change. This happens since it takes a little
bit of time for the schema change to propagate in the cluster and gossip info
in the node with the control connection might still have all nodes on the old
schema version and in that case the schema agreement check still return true.
For 3.x this was changed in
[JAVA-1140|https://datastax-oss.atlassian.net/browse/JAVA-1140] so the schema
agreement check after a DDL query is done on the same node as the DDL query.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
