cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (CASSANDRA-2474) CQL support for compound columns
Date Fri, 30 Dec 2011 01:43:33 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177293#comment-13177293
] 

Jonathan Ellis edited comment on CASSANDRA-2474 at 12/30/11 1:41 AM:
---------------------------------------------------------------------

I've updated the wiki page at http://wiki.apache.org/cassandra/Cassandra2474 with a more in-depth
Background section that hopefully clears up where I'm going with this sparse/dense business.

Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax implicitly using the first
element of PRIMARY KEY as the row key.  We could make it explicit with another WITH option
to the TRANSPOSED clause: 

{code}
CREATE TABLE timeline (
    user_id int,
    posted_at uuid,
    column string,
    value blob,    
    PRIMARY KEY(user_id, posted_at)
) TRANSPOSED WITH ROW KEY(user_id)
{code}

This makes things more verbose (this would be a required clause) but I'm okay with that if
consensus is that being explicit here is better.
                
      was (Author: jbellis):
    I've updated the wiki page at http://wiki.apache.org/cassandra/Cassandra2474 with a more
in-depth Background section that hopefully clears up where I'm going with this sparse/dense
business.

Eric mentioned on IRC that he's uneasy about the PRIMARY KEY syntax implicitly using the first
element of PRIMARY KEY as the row key.  We could make it explicit with another WITH option
to the TRANSPOSED clause: 

{{{
CREATE TABLE timeline (
    user_id int,
    posted_at uuid,
    column string,
    value blob,    
    PRIMARY KEY(user_id, posted_at)
) TRANSPOSED WITH ROW KEY(user_id)
}}}

This makes things more verbose (this would be a required clause) but I'm okay with that if
consensus is that being explicit here is better.
                  
> CQL support for compound columns
> --------------------------------
>
>                 Key: CASSANDRA-2474
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
>             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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message