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 Tue, 20 Dec 2011 20:25:31 GMT


Jonathan Ellis commented on CASSANDRA-2474:

bq. I didn't though the goal was to 'adapt to the relational philosophy'

All data is relational, the only question is implementation details. :)

Seriously though, "send a query, get back rows" is a good design for a language + driver,
and you simply can't represent slices of wide, composite rows sanely that way without something
like transposition to expose the structure "hidden" underneath.

bq. WITH comparator = composite(sender,thread,tid);

Wouldn't you need body in the composite list too?

bq. --Finally in the case of both SPARSE/DENSE

So this is basically what I gave, right?  It sounds like you're bikeshedding the TRANSPOSED
/ WITH COMPARATOR syntax but not really solving the problem I outlined.  Maybe I'm missing
> 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