Merge branch 'cassandra-3.X' into trunk * cassandra-3.X: Reject default_time_to_live option when creating or altering MVs
Project: http://git-wip-us.apache.org/repos/asf/cassandra/repo Commit: http://git-wip-us.apache.org/repos/asf/cassandra/commit/7e668271 Tree: http://git-wip-us.apache.org/repos/asf/cassandra/tree/7e668271 Diff: http://git-wip-us.apache.org/repos/asf/cassandra/diff/7e668271 Branch: refs/heads/trunk Commit: 7e668271a9b523224e7125bd79bce455a211746b Parents: ce631bd 918a062 Author: Sylvain Lebresne <[email protected]> Authored: Mon Dec 5 12:12:18 2016 +0100 Committer: Sylvain Lebresne <[email protected]> Committed: Mon Dec 5 12:12:18 2016 +0100 ---------------------------------------------------------------------- CHANGES.txt | 3 ++ NEWS.txt | 9 +++++ .../cql3/statements/AlterViewStatement.java | 8 ++++ .../cql3/statements/CreateViewStatement.java | 11 ++++- .../org/apache/cassandra/cql3/ViewTest.java | 42 ++++++++++++++++++++ 5 files changed, 72 insertions(+), 1 deletion(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cassandra/blob/7e668271/CHANGES.txt ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/cassandra/blob/7e668271/NEWS.txt ---------------------------------------------------------------------- diff --cc NEWS.txt index d838847,80a8797..4e212bb --- a/NEWS.txt +++ b/NEWS.txt @@@ -13,23 -13,15 +13,32 @@@ restore snapshots created with the prev 'sstableloader' tool. You can upgrade the file format of your snapshots using the provided 'sstableupgrade' tool. +4.0 +=== + +New features +------------ + +Upgrading +--------- + - Cassandra 4.0 removed support for any pre-3.0 format. This means you cannot upgrade from a 2.x version to 4.0 + directly, you have to upgrade to a 3.0.x/3.x version first (and run upgradesstable). In particular, this mean + Cassandra 4.0 cannot load or read pre-3.0 sstables in any way: you will need to upgrade those sstable in 3.0.x/3.x + first. + - Cassandra will no longer allow invalid keyspace replication options, such as invalid datacenter names for + NetworkTopologyStrategy. Operators MUST add new nodes to a datacenter before they can set set ALTER or + CREATE keyspace replication policies using that datacenter. Existing keyspaces will continue to operate, + but CREATE and ALTER will validate that all datacenters specified exist in the cluster. + + 3.11 + ==== + + Upgrading + --------- + - Specifying the default_time_to_live option when creating or altering a + materialized view was erroneously accepted (and ignored). It is now + properly rejected. + 3.10 ====
