[
https://issues.apache.org/jira/browse/CASSANDRA-12697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15516541#comment-15516541
]
Philip Thompson commented on CASSANDRA-12697:
---------------------------------------------
It's the same exception, with the error {{Unknown column cdc during
deserialization}}? Yeah, I 100% know why that's happening. When the original
ticket for that was first filed, TE was told it was harmless and to ignore it
in the tests. Looks like we never stopped ignoring it. Should I go ahead and
change the tests to remove the exemption for this error?
> cdc column addition still breaks schema migration tasks
> -------------------------------------------------------
>
> Key: CASSANDRA-12697
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12697
> Project: Cassandra
> Issue Type: Bug
> Components: Distributed Metadata
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Fix For: 3.x
>
>
> This is a followup of CASSANDRA-12236, which basically didn't fully fix the
> problem. Namely, the fix from CASSANDRA-12236 skipped the {{cdc}} column in
> {{SchemaKeyspace.addTableParamsToRowBuilder()}}, but that method isn't used
> by schema "migration tasks" ({{MigrationRequestVerbHandler}}, which instead
> directly send the content of the full schema table it reads from disk. So we
> still end up with a RTE like CASSANDRA-12236.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
