[ https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095618#comment-13095618 ]
Jonathan Ellis edited comment on CASSANDRA-2474 at 9/1/11 9:31 PM: ------------------------------------------------------------------- Illustration time. (See: screenshot-1.jpg) We have a "wide row" of stock histories. Just "normal" columns, no composites or supercolumns. We could use transposition syntax to get these as "normal" (not sparse) resultset: {code} SELECT date, price FROM stockhist WHERE symbol='GOOG' AND date >= '2011-01-02' LIMIT 50 {code} Which would yield {noformat} date price 2011-01-02 $75.23 2011-01-03 $82.11 {noformat} As mentioned above, we need to figure out how to allow adding the date/price aliases to refer to column name/value, and extend that to the more general composite column case. was (Author: jbellis): Illustration time. (See: screenshot-1.jpg) We have a "wide row" of stock histories. Just "normal" columns, no composites or supercolumns. We could use transposition syntax to get these as "normal" (not sparse) resultset: {code} SELECT date, value FROM stockhist WHERE symbol='GOOG' AND date >= '2011-01-02' LIMIT 50 {code} Which would yield {noformat} date value 2011-01-02 $75.23 2011-01-03 $82.11 {noformat} > CQL support for compound columns > -------------------------------- > > Key: CASSANDRA-2474 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2474 > Project: Cassandra > Issue Type: Sub-task > Components: API, Core > Reporter: Eric Evans > Assignee: Pavel Yaskevich > Labels: cql > Fix For: 1.0 > > Attachments: screenshot-1.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. For more information on JIRA, see: http://www.atlassian.com/software/jira