diff -u cassandra-2.2.6/debian/changelog cassandra-2.2.6/debian/changelog --- cassandra-2.2.6/debian/changelog +++ cassandra-2.2.6/debian/changelog @@ -1,3 +1,9 @@ +cassandra (2.2.6-wmf3) unstable; urgency=medium + + * Comment out JVM test invocation that blocks start up. + + -- Eric Evans Mon, 12 Mar 2018 11:06:06 -0500 + cassandra (2.2.6-wmf2) unstable; urgency=medium * Backported https://issues.apache.org/jira/browse/CASSANDRA-11752, only in patch2: unchanged: --- cassandra-2.2.6.orig/README.wmf.md +++ cassandra-2.2.6/README.wmf.md @@ -0,0 +1,57 @@ +Building Cassandra for Wikimedia +================================ + +### Cleanup any locally generated cruft + + $ rm -rf logs/ data/ + +### Create a release artifact in the expected format + + $ VERSION=2.2.6 + $ git archive --format=tar --prefix=cassandra-$VERSION/ \ + | gzip > ../cassandra_$VERSION.orig.tar.gz + +### Build a Debian package + + $ dpkg-buildpackage -rfakeroot -us -uc -i'\.git.*' + +Delta to 2.2.6 (release) +------------------------- + + commit c4dda2525fbe3c1f6f29fea8afa5bb6249d24070 + Author: Eric Evans + Date: Mon Mar 12 13:17:47 2018 -0500 + + prompt compiler to use utf-8 source encoding + + commit feb033b34195ad993b57ad5192dec4471fb58aa4 + Author: Eric Evans + Date: Mon Mar 12 11:07:21 2018 -0500 + + Update for 2.2.6-wmf3 Debian package release + + commit 3a5687f3d67240e0f6f260d9802b53ee52632e79 + Author: Eric Evans + Date: Mon Mar 12 10:57:37 2018 -0500 + + comment out startup test + + https://issues.apache.org/jira/browse/CASSANDRA-7254 added a pre-start + invocation of the JVM that blocks when using the Prometheus JMX exporter. This + patch comments out this invocation, since the condition the test checks for + should not be a problem in our environment. + + Bug: T186567 + + commit 9e94b97694c36d85ffc86e6ef00043758252df0f + Author: Eric Evans + Date: Mon Mar 12 10:49:04 2018 -0500 + + import WMF build (2.2.6-wmf2) + + commit e892e3e3ba1b687222915f1c4f523bb7d212d63f + Author: Eric Evans + Date: Mon Mar 12 10:51:54 2018 -0500 + + README.wmf.md + only in patch2: unchanged: --- cassandra-2.2.6.orig/build.xml +++ cassandra-2.2.6/build.xml @@ -798,6 +798,7 @@ + @@ -1156,7 +1157,8 @@ - + + only in patch2: unchanged: --- cassandra-2.2.6.orig/debian/patches/110remove_cassandra-7254_test.dpatch +++ cassandra-2.2.6/debian/patches/110remove_cassandra-7254_test.dpatch @@ -0,0 +1,31 @@ +#! /bin/sh /usr/share/dpatch/dpatch-run +## 110remove_cassandra-7254_test.dpatch by Eric Evans +## +## All lines beginning with `## DP:' are a description of the patch. +## DP: No description. + +@DPATCH@ +diff --git a/bin/cassandra b/bin/cassandra +index c968c35636..f5d87f4f4f 100755 +--- a/bin/cassandra ++++ b/bin/cassandra +@@ -257,12 +257,13 @@ while true; do + esac + done + +-# see CASSANDRA-7254 +-"$JAVA" -cp "$CLASSPATH" $JVM_OPTS 2>&1 | grep -q 'Error: Exception thrown by the agent : java.lang.NullPointerException' +-if [ $? -ne "1" ]; then +- echo Unable to bind JMX, is Cassandra already running? +- exit 1; +-fi ++# Blocks startup when using the Prometheus exporter agent (see: T186567) ++# # see CASSANDRA-7254 ++# "$JAVA" -cp "$CLASSPATH" $JVM_OPTS 2>&1 | grep -q 'Error: Exception thrown by the agent : java.lang.NullPointerException' ++# if [ $? -ne "1" ]; then ++# echo Unable to bind JMX, is Cassandra already running? ++# exit 1; ++# fi + + # Start up the service + launch_service "$pidfile" "$foreground" "$properties" "$classname" only in patch2: unchanged: --- cassandra-2.2.6.orig/doc/cql3/CQL.html +++ cassandra-2.2.6/doc/cql3/CQL.html @@ -644,4 +644,4 @@ INSERT INTO atable (pk, val) VALUES (4,4); SELECT average(val) FROM atable;

See CREATE AGGREGATE and DROP AGGREGATE.

JSON Support

Cassandra 2.2 introduces JSON support to SELECT and INSERT statements. This support does not fundamentally alter the CQL API (for example, the schema is still enforced), it simply provides a convenient way to work with JSON documents.

SELECT JSON

With SELECT statements, the new JSON keyword can be used to return each row as a single JSON encoded map. The remainder of the SELECT statment behavior is the same.

The result map keys are the same as the column names in a normal result set. For example, a statement like "SELECT JSON a, ttl(b) FROM ..." would result in a map with keys "a" and "ttl(b)". However, this is one notable exception: for symmetry with INSERT JSON behavior, case-sensitive column names with upper-case letters will be surrounded with double quotes. For example, "SELECT JSON myColumn FROM ..." would result in a map key "\"myColumn\"" (note the escaped quotes).

The map values will JSON-encoded representations (as described below) of the result set values.

INSERT JSON

With INSERT statements, the new JSON keyword can be used to enable inserting a JSON encoded map as a single row. The format of the JSON map should generally match that returned by a SELECT JSON statement on the same table. In particular, case-sensitive column names should be surrounded with double quotes. For example, to insert into a table with two columns named “myKey” and “value”, you would do the following:

INSERT INTO mytable JSON '{"\"myKey\"": 0, "value": 0}'
-

Any columns which are ommitted from the JSON map will be defaulted to a NULL value (which will result in a tombstone being created).

JSON Encoding of Cassandra Data Types

Where possible, Cassandra will represent and accept data types in their native JSON representation. Cassandra will also accept string representations matching the CQL literal format for all single-field types. For example, floats, ints, UUIDs, and dates can be represented by CQL literal strings. However, compound types, such as collections, tuples, and user-defined types must be represented by native JSON collections (maps and lists) or a JSON-encoded string representation of the collection.

The following table describes the encodings that Cassandra will accept in INSERT JSON values (and fromJson() arguments) as well as the format Cassandra will use when returning data for SELECT JSON statements (and fromJson()):

type	formats accepted	return format	notes
`ascii`	string	string	Uses JSON’s `\u` character escape
`bigint`	integer, string	integer	String must be valid 64 bit integer
`blob`	string	string	String should be 0x followed by an even number of hex digits
`boolean`	boolean, string	boolean	String must be “true” or "false"
`date`	string	string	Date in format `YYYY-MM-DD`, timezone UTC
`decimal`	integer, float, string	float	May exceed 32 or 64-bit IEEE-754 floating point precision in client-side decoder
`double`	integer, float, string	float	String must be valid integer or float
`float`	integer, float, string	float	String must be valid integer or float
`inet`	string	string	IPv4 or IPv6 address
`int`	integer, string	integer	String must be valid 32 bit integer
`list`	list, string	list	Uses JSON’s native list representation
`map`	map, string	map	Uses JSON’s native map representation
`smallint`	integer, string	integer	String must be valid 16 bit integer
`set`	list, string	list	Uses JSON’s native list representation
`text`	string	string	Uses JSON’s `\u` character escape
`time`	string	string	Time of day in format `HH-MM-SS[.fffffffff]`
`timestamp`	integer, string	string	A timestamp. Strings constant are allow to input timestamps as dates, see Working with dates below for more information. Datestamps with format `YYYY-MM-DD HH:MM:SS.SSS` are returned.
`timeuuid`	string	string	Type 1 UUID. See Constants for the UUID format
`tinyint`	integer, string	integer	String must be valid 8 bit integer
`tuple`	list, string	list	Uses JSON’s native list representation
`UDT`	map, string	map	Uses JSON’s native map representation with field names as keys
`uuid`	string	string	See Constants for the UUID format
`varchar`	string	string	Uses JSON’s `\u` character escape
`varint`	integer, string	integer	Variable length; may overflow 32 or 64 bit integers in client-side decoder

The fromJson() Function

The fromJson() function may be used similarly to INSERT JSON, but for a single column value. It may only be used in the VALUES clause of an INSERT statement or as one of the column values in an UPDATE, DELETE, or SELECT statement. For example, it cannot be used in the selection clause of a SELECT statement.

The toJson() Function

The toJson() function may be used similarly to SELECT JSON, but for a single column value. It may only be used in the selection clause of a SELECT statement.

Appendix A: CQL Keywords

CQL distinguishes between reserved and non-reserved keywords. Reserved keywords cannot be used as identifier, they are truly reserved for the language (but one can enclose a reserved keyword by double-quotes to use it as an identifier). Non-reserved keywords however only have a specific meaning in certain context but can used as identifer otherwise. The only raison d'être of these non-reserved keywords is convenience: some keyword are non-reserved when it was always easy for the parser to decide whether they were used as keywords or not.

Keyword	Reserved?
`ADD`	yes
`AGGREGATE`	no
`ALL`	no
`ALLOW`	yes
`ALTER`	yes
`AND`	yes
`APPLY`	yes
`AS`	no
`ASC`	yes
`ASCII`	no
`AUTHORIZE`	yes
`BATCH`	yes
`BEGIN`	yes
`BIGINT`	no
`BLOB`	no
`BOOLEAN`	no
`BY`	yes
`CALLED`	no
`CLUSTERING`	no
`COLUMNFAMILY`	yes
`COMPACT`	no
`CONTAINS`	no
`COUNT`	no
`COUNTER`	no
`CREATE`	yes
`CUSTOM`	no
`DATE`	no
`DECIMAL`	no
`DELETE`	yes
`DESC`	yes
`DESCRIBE`	yes
`DISTINCT`	no
`DOUBLE`	no
`DROP`	yes
`ENTRIES`	yes
`EXECUTE`	yes
`EXISTS`	no
`FILTERING`	no
`FINALFUNC`	no
`FLOAT`	no
`FROM`	yes
`FROZEN`	no
`FULL`	yes
`FUNCTION`	no
`FUNCTIONS`	no
`GRANT`	yes
`IF`	yes
`IN`	yes
`INDEX`	yes
`INET`	no
`INFINITY`	yes
`INITCOND`	no
`INPUT`	no
`INSERT`	yes
`INT`	no
`INTO`	yes
`JSON`	no
`KEY`	no
`KEYS`	no
`KEYSPACE`	yes
`KEYSPACES`	no
`LANGUAGE`	no
`LIMIT`	yes
`LIST`	no
`LOGIN`	no
`MAP`	no
`MODIFY`	yes
`NAN`	yes
`NOLOGIN`	no
`NORECURSIVE`	yes
`NOSUPERUSER`	no
`NOT`	yes
`NULL`	yes
`OF`	yes
`ON`	yes
`OPTIONS`	no
`OR`	yes
`ORDER`	yes
`PASSWORD`	no
`PERMISSION`	no
`PERMISSIONS`	no
`PRIMARY`	yes
`RENAME`	yes
`REPLACE`	yes
`RETURNS`	no
`REVOKE`	yes
`ROLE`	no
`ROLES`	no
`SCHEMA`	yes
`SELECT`	yes
`SET`	yes
`SFUNC`	no
`SMALLINT`	no
`STATIC`	no
`STORAGE`	no
`STYPE`	no
`SUPERUSER`	no
`TABLE`	yes
`TEXT`	no
`TIME`	no
`TIMESTAMP`	no
`TIMEUUID`	no
`TINYINT`	no
`TO`	yes
`TOKEN`	yes
`TRIGGER`	no
`TRUNCATE`	yes
`TTL`	no
`TUPLE`	no
`TYPE`	no
`UNLOGGED`	yes
`UPDATE`	yes
`USE`	yes
`USER`	no
`USERS`	no
`USING`	yes
`UUID`	no
`VALUES`	no
`VARCHAR`	no
`VARINT`	no
`WHERE`	yes
`WITH`	yes
`WRITETIME`	no

Appendix B: CQL Reserved Types

The following type names are not currently used by CQL, but are reserved for potential future use. User-defined types may not use reserved type names as their name.

type
`bitstring`
`byte`
`complex`
`date`
`enum`
`interval`
`macaddr`
`smallint`

Changes

The following describes the changes in each version of CQL.

3.3.1

The syntax TRUNCATE TABLE X is now accepted as an alias for TRUNCATE X

3.3.0

Adds new aggregates
User-defined functions are now supported through CREATE FUNCTION and DROP FUNCTION.
User-defined aggregates are now supported through CREATE AGGREGATE and DROP AGGREGATE.
Allows double-dollar enclosed strings literals as an alternative to single-quote enclosed strings.
Introduces Roles to supercede user based authentication and access control
Date and Time data types have been added
JSON support has been added
Tinyint and Smallint data types have been added
Adds new time conversion functions and deprecate dateOf and unixTimestampOf. See Time conversion functions

3.2.0

User-defined types are now supported through CREATE TYPE, ALTER TYPE, and DROP TYPE
CREATE INDEX now supports indexing collection columns, including indexing the keys of map collections through the keys() function
Indexes on collections may be queried using the new CONTAINS and CONTAINS KEY operators
Tuple types were added to hold fixed-length sets of typed positional fields (see the section on types )
DROP INDEX now supports optionally specifying a keyspace

3.1.7

SELECT statements now support selecting multiple rows in a single partition using an IN clause on combinations of clustering columns. See SELECT WHERE clauses.
IF NOT EXISTS and IF EXISTS syntax is now supported by CREATE USER and DROP USER statmenets, respectively.

3.1.6

A new uuid method has been added.
Support for DELETE ... IF EXISTS syntax.

3.1.5

It is now possible to group clustering columns in a relatiion, see SELECT WHERE clauses.
Added support for STATIC columns, see static in CREATE TABLE.

3.1.4

CREATE INDEX now allows specifying options when creating CUSTOM indexes (see CREATE INDEX reference ).

3.1.3

Millisecond precision formats have been added to the timestamp parser (see working with dates ).

3.1.2

NaN and Infinity has been added as valid float contants. They are now reserved keywords. In the unlikely case you we using them as a column identifier (or keyspace/table one), you will noew need to double quote them (see quote identifiers ).

3.1.1

SELECT statement now allows listing the partition keys (using the DISTINCT modifier). See CASSANDRA-4536.
The syntax c IN ? is now supported in WHERE clauses. In that case, the value expected for the bind variable will be a list of whatever type c is.
It is now possible to use named bind variables (using :name instead of ?).

3.1.0

ALTER TABLE DROP option has been reenabled for CQL3 tables and has new semantics now: the space formerly used by dropped columns will now be eventually reclaimed (post-compaction). You should not readd previously dropped columns unless you use timestamps with microsecond precision (see CASSANDRA-3919 for more details).
SELECT statement now supports aliases in select clause. Aliases in WHERE and ORDER BY clauses are not supported. See the section on select for details.
CREATE statements for KEYSPACE, TABLE and INDEX now supports an IF NOT EXISTS condition. Similarly, DROP statements support a IF EXISTS condition.
INSERT statements optionally supports a IF NOT EXISTS condition and UPDATE supports IF conditions.

3.0.5

SELECT, UPDATE, and DELETE statements now allow empty IN relations (see CASSANDRA-5626).

3.0.4

Updated the syntax for custom secondary indexes.
Non-equal condition on the partition key are now never supported, even for ordering partitioner as this was not correct (the order was not the one of the type of the partition key). Instead, the token method should always be used for range queries on the partition key (see WHERE clauses ).

3.0.3

Support for custom secondary indexes has been added.

3.0.2

Type validation for the constants has been fixed. For instance, the implementation used to allow '2' as a valid value for an int column (interpreting it has the equivalent of 2), or 42 as a valid blob value (in which case 42 was interpreted as an hexadecimal representation of the blob). This is no longer the case, type validation of constants is now more strict. See the data types section for details on which constant is allowed for which type.
The type validation fixed of the previous point has lead to the introduction of blobs constants to allow inputing blobs. Do note that while inputing blobs as strings constant is still supported by this version (to allow smoother transition to blob constant), it is now deprecated (in particular the data types section does not list strings constants as valid blobs) and will be removed by a future version. If you were using strings as blobs, you should thus update your client code ASAP to switch blob constants.
A number of functions to convert native types to blobs have also been introduced. Furthermore the token function is now also allowed in select clauses. See the section on functions for details.

3.0.1

Date strings (and timestamps) are no longer accepted as valid timeuuid values. Doing so was a bug in the sense that date string are not valid timeuuid, and it was thus resulting in confusing behaviors. However, the following new methods have been added to help working with timeuuid: now, minTimeuuid, maxTimeuuid , dateOf and unixTimestampOf. See the section dedicated to these methods for more detail.
“Float constants”#constants now support the exponent notation. In other words, 4.2E10 is now a valid floating point value.

Versioning

Versioning of the CQL language adheres to the Semantic Versioning guidelines. Versions take the form X.Y.Z where X, Y, and Z are integer values representing major, minor, and patch level respectively. There is no correlation between Cassandra release versions and the CQL language version.

version	description
Major	The major version must be bumped when backward incompatible changes are introduced. This should rarely occur.
Minor	Minor version increments occur when new, but backward compatible, functionality is introduced.
Patch	The patch version is incremented when bugs are fixed.

\ No newline at end of file +

Any columns which are ommitted from the JSON map will be defaulted to a NULL value (which will result in a tombstone being created).

JSON Encoding of Cassandra Data Types

type	formats accepted	return format	notes
`ascii`	string	string	Uses JSON’s `\u` character escape
`bigint`	integer, string	integer	String must be valid 64 bit integer
`blob`	string	string	String should be 0x followed by an even number of hex digits
`boolean`	boolean, string	boolean	String must be “true” or "false"
`date`	string	string	Date in format `YYYY-MM-DD`, timezone UTC
`decimal`	integer, float, string	float	May exceed 32 or 64-bit IEEE-754 floating point precision in client-side decoder
`double`	integer, float, string	float	String must be valid integer or float
`float`	integer, float, string	float	String must be valid integer or float
`inet`	string	string	IPv4 or IPv6 address
`int`	integer, string	integer	String must be valid 32 bit integer
`list`	list, string	list	Uses JSON’s native list representation
`map`	map, string	map	Uses JSON’s native map representation
`smallint`	integer, string	integer	String must be valid 16 bit integer
`set`	list, string	list	Uses JSON’s native list representation
`text`	string	string	Uses JSON’s `\u` character escape
`time`	string	string	Time of day in format `HH-MM-SS[.fffffffff]`
`timestamp`	integer, string	string	A timestamp. Strings constant are allow to input timestamps as dates, see Working with dates below for more information. Datestamps with format `YYYY-MM-DD HH:MM:SS.SSS` are returned.
`timeuuid`	string	string	Type 1 UUID. See Constants for the UUID format
`tinyint`	integer, string	integer	String must be valid 8 bit integer
`tuple`	list, string	list	Uses JSON’s native list representation
`UDT`	map, string	map	Uses JSON’s native map representation with field names as keys
`uuid`	string	string	See Constants for the UUID format
`varchar`	string	string	Uses JSON’s `\u` character escape
`varint`	integer, string	integer	Variable length; may overflow 32 or 64 bit integers in client-side decoder

The fromJson() Function

The toJson() Function

The toJson() function may be used similarly to SELECT JSON, but for a single column value. It may only be used in the selection clause of a SELECT statement.

Appendix A: CQL Keywords

CQL distinguishes between reserved and non-reserved keywords. Reserved keywords cannot be used as identifier, they are truly reserved for the language (but one can enclose a reserved keyword by double-quotes to use it as an identifier). Non-reserved keywords however only have a specific meaning in certain context but can used as identifer otherwise. The only raison d'��tre of these non-reserved keywords is convenience: some keyword are non-reserved when it was always easy for the parser to decide whether they were used as keywords or not.

Keyword	Reserved?
`ADD`	yes
`AGGREGATE`	no
`ALL`	no
`ALLOW`	yes
`ALTER`	yes
`AND`	yes
`APPLY`	yes
`AS`	no
`ASC`	yes
`ASCII`	no
`AUTHORIZE`	yes
`BATCH`	yes
`BEGIN`	yes
`BIGINT`	no
`BLOB`	no
`BOOLEAN`	no
`BY`	yes
`CALLED`	no
`CLUSTERING`	no
`COLUMNFAMILY`	yes
`COMPACT`	no
`CONTAINS`	no
`COUNT`	no
`COUNTER`	no
`CREATE`	yes
`CUSTOM`	no
`DATE`	no
`DECIMAL`	no
`DELETE`	yes
`DESC`	yes
`DESCRIBE`	yes
`DISTINCT`	no
`DOUBLE`	no
`DROP`	yes
`ENTRIES`	yes
`EXECUTE`	yes
`EXISTS`	no
`FILTERING`	no
`FINALFUNC`	no
`FLOAT`	no
`FROM`	yes
`FROZEN`	no
`FULL`	yes
`FUNCTION`	no
`FUNCTIONS`	no
`GRANT`	yes
`IF`	yes
`IN`	yes
`INDEX`	yes
`INET`	no
`INFINITY`	yes
`INITCOND`	no
`INPUT`	no
`INSERT`	yes
`INT`	no
`INTO`	yes
`JSON`	no
`KEY`	no
`KEYS`	no
`KEYSPACE`	yes
`KEYSPACES`	no
`LANGUAGE`	no
`LIMIT`	yes
`LIST`	no
`LOGIN`	no
`MAP`	no
`MODIFY`	yes
`NAN`	yes
`NOLOGIN`	no
`NORECURSIVE`	yes
`NOSUPERUSER`	no
`NOT`	yes
`NULL`	yes
`OF`	yes
`ON`	yes
`OPTIONS`	no
`OR`	yes
`ORDER`	yes
`PASSWORD`	no
`PERMISSION`	no
`PERMISSIONS`	no
`PRIMARY`	yes
`RENAME`	yes
`REPLACE`	yes
`RETURNS`	no
`REVOKE`	yes
`ROLE`	no
`ROLES`	no
`SCHEMA`	yes
`SELECT`	yes
`SET`	yes
`SFUNC`	no
`SMALLINT`	no
`STATIC`	no
`STORAGE`	no
`STYPE`	no
`SUPERUSER`	no
`TABLE`	yes
`TEXT`	no
`TIME`	no
`TIMESTAMP`	no
`TIMEUUID`	no
`TINYINT`	no
`TO`	yes
`TOKEN`	yes
`TRIGGER`	no
`TRUNCATE`	yes
`TTL`	no
`TUPLE`	no
`TYPE`	no
`UNLOGGED`	yes
`UPDATE`	yes
`USE`	yes
`USER`	no
`USERS`	no
`USING`	yes
`UUID`	no
`VALUES`	no
`VARCHAR`	no
`VARINT`	no
`WHERE`	yes
`WITH`	yes
`WRITETIME`	no

Appendix B: CQL Reserved Types

The following type names are not currently used by CQL, but are reserved for potential future use. User-defined types may not use reserved type names as their name.

type
`bitstring`
`byte`
`complex`
`date`
`enum`
`interval`
`macaddr`
`smallint`

Changes

The following describes the changes in each version of CQL.

3.3.1

The syntax TRUNCATE TABLE X is now accepted as an alias for TRUNCATE X

3.3.0

Adds new aggregates
User-defined functions are now supported through CREATE FUNCTION and DROP FUNCTION.
User-defined aggregates are now supported through CREATE AGGREGATE and DROP AGGREGATE.
Allows double-dollar enclosed strings literals as an alternative to single-quote enclosed strings.
Introduces Roles to supercede user based authentication and access control
Date and Time data types have been added
JSON support has been added
Tinyint and Smallint data types have been added
Adds new time conversion functions and deprecate dateOf and unixTimestampOf. See Time conversion functions

3.2.0

User-defined types are now supported through CREATE TYPE, ALTER TYPE, and DROP TYPE
CREATE INDEX now supports indexing collection columns, including indexing the keys of map collections through the keys() function
Indexes on collections may be queried using the new CONTAINS and CONTAINS KEY operators
Tuple types were added to hold fixed-length sets of typed positional fields (see the section on types )
DROP INDEX now supports optionally specifying a keyspace

3.1.7

SELECT statements now support selecting multiple rows in a single partition using an IN clause on combinations of clustering columns. See SELECT WHERE clauses.
IF NOT EXISTS and IF EXISTS syntax is now supported by CREATE USER and DROP USER statmenets, respectively.

3.1.6

A new uuid method has been added.
Support for DELETE ... IF EXISTS syntax.

3.1.5

It is now possible to group clustering columns in a relatiion, see SELECT WHERE clauses.
Added support for STATIC columns, see static in CREATE TABLE.

3.1.4

CREATE INDEX now allows specifying options when creating CUSTOM indexes (see CREATE INDEX reference ).

3.1.3

Millisecond precision formats have been added to the timestamp parser (see working with dates ).

3.1.2

NaN and Infinity has been added as valid float contants. They are now reserved keywords. In the unlikely case you we using them as a column identifier (or keyspace/table one), you will noew need to double quote them (see quote identifiers ).

3.1.1

SELECT statement now allows listing the partition keys (using the DISTINCT modifier). See CASSANDRA-4536.
The syntax c IN ? is now supported in WHERE clauses. In that case, the value expected for the bind variable will be a list of whatever type c is.
It is now possible to use named bind variables (using :name instead of ?).

3.1.0

ALTER TABLE DROP option has been reenabled for CQL3 tables and has new semantics now: the space formerly used by dropped columns will now be eventually reclaimed (post-compaction). You should not readd previously dropped columns unless you use timestamps with microsecond precision (see CASSANDRA-3919 for more details).
SELECT statement now supports aliases in select clause. Aliases in WHERE and ORDER BY clauses are not supported. See the section on select for details.
CREATE statements for KEYSPACE, TABLE and INDEX now supports an IF NOT EXISTS condition. Similarly, DROP statements support a IF EXISTS condition.
INSERT statements optionally supports a IF NOT EXISTS condition and UPDATE supports IF conditions.

3.0.5

SELECT, UPDATE, and DELETE statements now allow empty IN relations (see CASSANDRA-5626).

3.0.4

Updated the syntax for custom secondary indexes.
Non-equal condition on the partition key are now never supported, even for ordering partitioner as this was not correct (the order was not the one of the type of the partition key). Instead, the token method should always be used for range queries on the partition key (see WHERE clauses ).

3.0.3

Support for custom secondary indexes has been added.

3.0.2

Type validation for the constants has been fixed. For instance, the implementation used to allow '2' as a valid value for an int column (interpreting it has the equivalent of 2), or 42 as a valid blob value (in which case 42 was interpreted as an hexadecimal representation of the blob). This is no longer the case, type validation of constants is now more strict. See the data types section for details on which constant is allowed for which type.
The type validation fixed of the previous point has lead to the introduction of blobs constants to allow inputing blobs. Do note that while inputing blobs as strings constant is still supported by this version (to allow smoother transition to blob constant), it is now deprecated (in particular the data types section does not list strings constants as valid blobs) and will be removed by a future version. If you were using strings as blobs, you should thus update your client code ASAP to switch blob constants.
A number of functions to convert native types to blobs have also been introduced. Furthermore the token function is now also allowed in select clauses. See the section on functions for details.

3.0.1

Date strings (and timestamps) are no longer accepted as valid timeuuid values. Doing so was a bug in the sense that date string are not valid timeuuid, and it was thus resulting in confusing behaviors. However, the following new methods have been added to help working with timeuuid: now, minTimeuuid, maxTimeuuid , dateOf and unixTimestampOf. See the section dedicated to these methods for more detail.
“Float constants”#constants now support the exponent notation. In other words, 4.2E10 is now a valid floating point value.

Versioning

version	description
Major	The major version must be bumped when backward incompatible changes are introduced. This should rarely occur.
Minor	Minor version increments occur when new, but backward compatible, functionality is introduced.
Patch	The patch version is incremented when bugs are fixed.