[
https://issues.apache.org/jira/browse/CASSANDRA-12236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385582#comment-15385582
]
Sylvain Lebresne commented on CASSANDRA-12236:
----------------------------------------------
Conditionally adding the cdc param only if cdc is enabled and tell user "don't
enable cdc until everything is on 3.8+" sounds simple and reasonable to me
(until we have a better way to handle those schema changes that is).
Ignoring unknown columns at deserialization is in fact much trickier since
deserializing the value depends on the type of the column, and we can't really
infer that out of thin air.
> RTE from new CDC column breaks in flight queries.
> -------------------------------------------------
>
> Key: CASSANDRA-12236
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12236
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jeremiah Jordan
> Priority: Blocker
> Fix For: 3.8
>
>
> This RTE is not harmless. It will cause the internode connection to break
> which will cause all in flight requests between these nodes to die/timeout.
> {noformat}
> - Due to changes in schema migration handling and the storage format
> after 3.0, you will
> see error messages such as:
> "java.lang.RuntimeException: Unknown column cdc during
> deserialization"
> in your system logs on a mixed-version cluster during upgrades. This
> error message
> is harmless and due to the 3.8 nodes having cdc added to their schema
> tables while
> the <3.8 nodes do not. This message should cease once all nodes are
> upgraded to 3.8.
> As always, refrain from schema changes during cluster upgrades.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
