[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095977#comment-13095977
]
Pavel Yaskevich commented on CASSANDRA-2474:
--------------------------------------------
bq. Please give an example then, preferably using either the tweet or stockhist
examples, of how this syntax improves things.
Using "ComponentX"
{noformat}
SELECT component1 AS tweet_id, component2 AS username, component3 location,
value AS body
FROM timeline:transposed
WHERE user_id = '95a789a'
{noformat}
vs. (..,..,..) notation from my previous comments
{noformat}
SELECT name AS (tweet_id, username, location), value AS body
FROM timeline:transposed
WHERE tweet_id = '95a789a'
{noformat}
bq. Yes, because the goal is to go from a resultset like this
Oh, I see now, we will need to delete old column any time we would need to add
or remove name component...
> 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
