[ https://issues.apache.org/jira/browse/CASSANDRA-18358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704188#comment-17704188 ]
Brandon Williams commented on CASSANDRA-18358: ---------------------------------------------- bq. rewrite the data so that the additional column is removed. This is an expensive process. I don't think the expense should be too much of a concern for system.local? > Fix issue with system.local.broadcast_port when downgrading to v3 > ----------------------------------------------------------------- > > Key: CASSANDRA-18358 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18358 > Project: Cassandra > Issue Type: Bug > Reporter: Claude Warren > Priority: Normal > > {{system.local}} table 4.0 format adds the {{broadcast_port}} column. There > is no way to make 3.x ignore it when we try to downgrade. > There are some tables that are defined in code. (e.g. system.local) > When v3 sstable schema for these tables detects: > * a column in the sstable schema that is not in the data schema it creates a > deleted column in the data schema. > * a column in the data schema that is not in the sstable schema it throws an > exception. > > There are two basic approaches to solve this: > * rewrite the data so that the additional column is removed. This is an > expensive process. > * rework the code so that columns in the data but not in the table are > ignored for this class of tables (statically defined in code). -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org