diff --git a/CHANGES.txt b/CHANGES.txt index ab3b662f6a..02a0be0571 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 5.1 + * Implementation of CEP-43 (CASSANDRA-19964) * Periodically disconnect roles that are revoked or have LOGIN=FALSE set (CASSANDRA-19385) * AST library for CQL-based fuzz tests (CASSANDRA-20198) * Support audit logging for JMX operations (CASSANDRA-20128) diff --git a/NEWS.txt b/NEWS.txt index 22921153da..a4cec79660 100644 --- a/NEWS.txt +++ b/NEWS.txt @@ -107,6 +107,8 @@ New features JMX to JVM parameters. You have to opt-in to use the configuration via cassandra.yaml by uncommenting the respective configuration sections and by commenting out `configure_jmx` function call in cassandra-env.sh. Enabling both ways of configuring JMX will result in a node failing to start. + - CEP-43 - it is possible to create a table by "copying" as `CREATE TABLE ks.tb_copy LIKE ks.tb;`. + A newly created table will have no data. Upgrading --------- diff --git a/doc/cql3/CQL.textile b/doc/cql3/CQL.textile index 4c2b09acc3..f819ec193d 100644 --- a/doc/cql3/CQL.textile +++ b/doc/cql3/CQL.textile @@ -406,6 +406,39 @@ h4. Other considerations: * When "inserting":#insertStmt / "updating":#updateStmt a given row, not all columns needs to be defined (except for those part of the key), and missing columns occupy no space on disk. Furthermore, adding new columns (see ALTER TABLE) is a constant time operation. There is thus no need to try to anticipate future usage (or to cry when you haven't) when creating a table. +h3(#copyStmt). CREATE TABLE LIKE + +__Syntax:__ + +bc(syntax).. + ::= CREATE ( TABLE | COLUMNFAMILY ) ( IF NOT EXISTS )? LIKE + ( WITH