cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Mon, 19 Dec 2011 14:17:32 GMT


T Jake Luciani commented on CASSANDRA-2474:

In the non-sparse case you always would always ignore the column value? I think we need to
expose that somehow. (first non-transposed, non-key, non-sparse column?)

Overall I like this because it forces a user to think at schema creation time and not access
time. This approach makes sense for CQL only access, but for users who are coming from thrift
they will be asking "how do i access data from my current data model?"

On the negative side, this approach feels a bit too restrictive since you *MUST* use the same
kind of schema across all rows within a CF.  What if a user doesn't know what the sparse columns
will be ahead of time?  

Also, I know that's best practice but want to make the point, what if a user wants to access
data in composite form and "raw" mode, should we support multiple "views" on the CF?

> 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: 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