[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098922#comment-13098922
]
Pavel Yaskevich commented on CASSANDRA-2474:
--------------------------------------------
how about this?
{noformat}
-- sparse select example
SELECT TRANSPOSE NAME TO (tweet_id; username, body; location) FROM tweets WHERE
key = <key> AND username = 'xedin';
-- dense select example
SELECT TRANSPOSE NAME TO (tweet_id; username; location) FROM tweets WHERE key =
<key> AND username = 'xedin';
-- insert
INSERT INTO tweets (KEY, COMPOUND NAME ('2e1c3308', username)) VALUES (<key>,
'cscotta');
INSERT INTO tweets (KEY, COMPOUND NAME ('2e1c3308', body)) VALUES (<key>,
'Brother...');
INSERT INTO tweets (KEY, COMPOUND NAME ('2e1c3308', 'cscotta')) VALUES (<key>,
'Brother...');
-- update
UPDATE tweets SET COMPOUND NAME ('2e1c3308', 'cscotta') = 'My motocycle...'
WHERE KEY = <key>;
{noformat}
> 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
