cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns
Date Fri, 02 Sep 2011 13:40:10 GMT


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"

SELECT component1 AS tweet_id, component2 AS username, component3 location, value AS body
FROM timeline:transposed
WHERE user_id = '95a789a'

vs. (..,..,..) notation from my previous comments

SELECT name AS (tweet_id, username, location), value AS body
FROM timeline:transposed
WHERE tweet_id = '95a789a'

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

> CQL support for compound columns
> --------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             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:


View raw message