[ https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097184#comment-13097184 ]
Sylvain Lebresne commented on CASSANDRA-2474: --------------------------------------------- Well, the timestamp was not meant to be the key in my example and the event_id needs to be the last component for this to make sense (since it is not specified in the query) but ok.. Now, I don't understand how: {noformat} SELECT name AS (category, subcategory, *), value AS event FROM events WHERE key = <timestamp> AND category = <category> AND subcategory = <subcat>; {noformat} is fundamentally different from {noformat} SELECT <category>:<subcat>:<event_id>, value FROM events WHERE key = <timestamp>; {noformat} which is roughly the proposition from CASSANDRA-2025. And I mean fundamentally different, not just from a syntax point of view (I have nothing against using parenthesis). If if it just a syntax difference, then fine. Or how {noformat} SELECT name AS (category, *), value AS event FROM events WHERE key = <timestamp> AND category > c1 AND category < c2; {noformat} is fundamentally different from {noformat} SELECT c1:*..c2:*, value FROM events WHERE key = <timestamp>; {noformat} Maybe giving an example of what is supposed to be the returned would start to show the differences, but so far it seems only a difference of syntax. And the discussions above suggests that there is more than that underneath. > 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, 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. For more information on JIRA, see: http://www.atlassian.com/software/jira