[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097258#comment-13097258
]
Pavel Yaskevich commented on CASSANDRA-2474:
--------------------------------------------
@Sylvain
it is going to return
{noformat}
Key | category | subc1 | subc2 | subc3 |
<timestamp> | c1 | event_value1 | | event_value3 |
<timestamp> | c2 | event_value4 | event_value2 | |
{noformat}
@Jonathan
bq. I don't understand, that seems perfectly readable to me. This syntax is not
viable for the reasons given in my previous comment. I'm happy to entertain
other alternatives to the component syntax but there's no need to spend further
time on this one.
I don't seem that readable to me. We can resolve this question by writing email
to the cassandra mailing list and let people decide.
> 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
