[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095626#comment-13095626
]
Pavel Yaskevich commented on CASSANDRA-2474:
--------------------------------------------
How about we do syntax like this:
for Standard columns
{noformat}
SELECT :column as date, :value as price FROM stockhist WHERE <key_alias>='GOOG'
AND date >= '2011-01-02' LIMIT 50
{noformat}
for Super columns
{noformat}
SELECT :parent as company, :column as date, :value as price FROM stockhist
WHERE company='GOOG' AND date >= '2011-01-02' AND <key_alias> = '...' LIMIT 50
{noformat}
for composite columns
{noformat}
SELECT :component as company, :component as date, :value as price FROM
stockhist WHERE company='GOOG' AND date >= '2011-01-02' AND <key_alias> = '...'
LIMIT 50
{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
>
>
> 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
