[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095968#comment-13095968
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. I hope that the main goal here is to give end-user clean syntax instead of
trying to be as SQL as possible in all the cases.
Please give an example then, preferably using either the tweet or stockhist
examples, of how this syntax improves things.
bq. Is there any reason why we should delete "2e1c3308,cscotta" I'm missing?
Yes, because the goal is to go from a resultset like this
{code}
tweet_id username body
2e1c3308 cscotta Brother...
2debb66c Werner Why ...
2f941d9a hlship Igor ...
{code}
To this:
{code}
tweet_id username body location
2e1c3308 cscotta Brother... CA
2debb66c Werner Why ...
2f941d9a hlship Igor ...
{code}
Not this:
{code}
tweet_id username body location
2e1c3308 cscotta Brother... CA
2e1c3308 cscotta Brother...
2debb66c Werner Why ...
2f941d9a hlship Igor ...
{code}
> 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
