[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046834#comment-13046834
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
I now think the original idea from CASSANDRA-2025 of "SELECT columnA:x,
columnA:y FROM foo WHERE key = 'bar'" is the wrong way to go. Instead, moving
the compoundness-specifier to the "column parent" is a better fit:
{quote}
SELECT x, y, FROM foo:bar WHERE parent='columnA'
{quote}
(Note that "parent" would be a configurable alias, a la key_alias today.) This
generalizes to deeper nesting, if we wish to support that:
{quote}
select a, b FROM foo:bar:columnA where subparent='x'
{quote}
This is both a better match for existing supercolumn semantics (so translation
to StorageProxy requests is straightforward) as well as a better fit for APIs
designed for SQL like JDBC.
> 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
> Labels: cql
> Fix For: 1.0
>
>
> 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
