Query: schema mismatch

[Maev4l]

Hi folks,

I have a question. Based on my understanding, when DDL statements are ran against Cassandra, we have to wait until the schema changes are propagated throughout the cluster, as all nodes need to agree on the schema version for proper operation. Otherwise, we have a schema disagreement in the cluster, which can cause all sorts of issues.
I think this the reason why we are provided with the SchemaChangeListener interface (https://docs.datastax.com/en/drivers/java/2.0/com/datastax/driver/core/SchemaChangeListener.html)
Therefore, I am wondering how this situation is managed by the liquidbase-cassandra extension. Is it already managed somewhere ? If it is not the case, are you aware of this potential problem ?

Best regards,

┆Issue is synchronized with this Jira Bug by Unito

[NicoHeller]

I am asking myself the same question, as I often read that it is not a good idea to do schema changes in Cassandra programmatically.