cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Mon, 19 Dec 2011 22:11:30 GMT


Pavel Yaskevich commented on CASSANDRA-2474:

Here is another option for this:

TRANSPOSED AS (<column> ?MODIFIER(<comparator>), ....) 

where MODIFIER = SPARSE | DENSE and <comparator> = utf8, int, uuid, timeuuid, ...; if
no MODIFIER set then MODIFIER = DENSE(default_type)

CREATE TABLE timeline (
    userid int primary key,
    posted_at uuid,
    posted_by int,
    body text,
    "92d21d0a-d6cb-437c-9d3f-b67aa733a19f" bigint
) TRANSPOSED AS (posted_at, posted_by SPARSE, 92d21d0a-d6cb-437c-9d3f-b67aa733a19f" DENSE(uuid),
body SPARSE);
> 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.PNG,
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