> If an upgrade involves changing the schema, I think backwards compatibility > would be out of the question?
That’s a good point. I just noticed that during the upgrade, the output of “nodetool describecluster” showed a schema version disagreement, where the nodes running 3.11.14 were on one schema version and the nodes running 4.1.3 were on a different schema version. When a node got upgraded, it moved to the new schema version. This made me think that the schema change was caused by the upgrade (in particular because we definitely did not make any manual schema changes during that period).
smime.p7s
Description: S/MIME cryptographic signature
