Repository: cassandra Updated Branches: refs/heads/trunk 4ae198765 -> 09103eeac
Explain errors during schema migration on mixed-version clusters post 3.0 Patch by jmckenzie; reviewed by cyeksigian for CASSANDRA-12026 Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/09103eea Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/09103eea Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/09103eea Branch: refs/heads/trunk Commit: 09103eeac93291a193db9a39b8a68964aacfe4d2 Parents: 4ae1987 Author: Josh McKenzie <[email protected]> Authored: Wed Jun 22 13:24:40 2016 -0400 Committer: Josh McKenzie <[email protected]> Committed: Wed Jun 22 13:24:40 2016 -0400 ---------------------------------------------------------------------- NEWS.txt | 7 +++++++ 1 file changed, 7 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cassandra/blob/09103eea/NEWS.txt ---------------------------------------------------------------------- diff --git a/NEWS.txt b/NEWS.txt index d34613c..7418f3a 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -48,6 +48,13 @@ Upgrading those under a different name, change your code to use the new names and drop the old versions, and this _before_ upgrade (see CASSANDRA-10783 for more details). + - 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. Deprecation -----------
