cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Dusbabek (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns and wide rows
Date Fri, 13 Jan 2012 22:54:40 GMT


Gary Dusbabek commented on CASSANDRA-2474:

bq. The '..' notation for slices is removed
-1. We at Rackspace use this extensively.  Also, pre-emptive -1 on supporting it for one more
version and then removing it.

bq. I've made static definitions (i.e, those definitions that don't use COMPACT STORAGE basically)
really static.
-1.  The two reasons you gave are subjective.  IMO (also subjective), they're not strong enough
for introducing backwards-incompatible changes.

bq. I'm going to make all column definition case insensitive
Ugh: "because PGSQL does it."  How about we leave them the way they are BECAUSE USERS EXPECT

I think CQL developers have forgotten that people are actually using CQL and are using it
because it is a more compelling interface than the old thrift.  If this API changes as often
as the thrift API did (and it is beginning to look that way), what have we gained?
> CQL support for compound columns and wide rows
> ----------------------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>              Labels: cql
>             Fix For: 1.1
>         Attachments: 0001-Add-support-for-wide-and-composite-CFs.patch, 0002-thrift-generated-code.patch,
2474-transposed-1.PNG, 2474-transposed-raw.PNG, 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG,, raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg
> For the most part, this boils down to supporting the specification of compound column
names (the CQL syntax is colon-delimted terms), and then teaching the decoders (drivers) to
create structures from the results.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message