cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Thu, 05 Jan 2012 14:01:40 GMT


Jonathan Ellis commented on CASSANDRA-2474:

bq. the only thing that is missing for the current schema is that 'column name alias' is "url".
And to support composites we basically need to make that alias a list. So overall it sounds
just like one field for CfDef. 

Agreed, that's what I came up with before I fell asleep last night too. :)

bq. my preference would go to not adding it to CfDef as Thrift doesn't care about aliases

I think we need to though, since that's how everyone learns the schema until CASSANDRA-2477
is done.  (Although CASSANDRA-1391 changes the internal storage enough that it may make 2477
easy.  Guess reviewing that is at the top of my list today.)
> CQL support for compound columns
> --------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Eric Evans
>            Assignee: Pavel Yaskevich
>              Labels: cql
>             Fix For: 1.1
>         Attachments: 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