[CASSANDRA-3761] CQL 3.0

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: Legacy/CQL
• Labels: cql
• Assignee: Sylvain Lebresne Assign to me
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Eric Evans

• Created: 20/Jan/12 16:14
• Updated: 16/Apr/19 09:32
• Resolved: 27/Nov/12 15:14

Description

This ticket is a reformulation/generalization of CASSANDRA-2474. The core change of CQL 3.0 is to introduce the new syntaxes that were discussed in CASSANDRA-2474 that allow to:

1. Provide a better/more native support for wide rows, using the idea of transposed vie.
2. The generalization to composite columns.

The attached text file create_cf_syntaxes.txt recall the new syntaxes introduced.

The changes proposed above allow (and strongly suggest in some cases) a number of other changes to the language that this ticket proposes to explore/implement (more details coming in the comments).

Sub-Tasks

• KEY IN (...) queries do not work: Resolved
• need forked language document: Resolved
• cassandra defaults to CQLv3: Resolved
• Secondary indexes support for wide rows in CQL 3.0: Resolved
• Add Support for Composite Secondary Indexes: Resolved
• Add 'null' support to CQL 3.0: Resolved
• Add KeyspaceChange CqlResultType: Resolved
• Support query by names for compact CF: Resolved
• Allow paging through non-ordered partitioner results in CQL3: Resolved
• Support slice with exclusive start and stop: Resolved
• CQL count() needs paging support: Resolved
• Dropping a column should do more than just remove the definition: Resolved
• ORDER BY syntax: Resolved
• Consider providing error code with exceptions (and documenting them): Resolved
• Explore not returning range ghosts: Resolved
• cqlsh support for CQL 3: Resolved
• Add support for ReversedType: Resolved
• Allow updating column_alias types: Resolved
• Support for sharding wide rows in CQL 3.0: Resolved
• Add more general support for composites (to row key, column value): Resolved
• Easy access to column timestamps (and maybe ttl) during queries: Resolved