[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13047357#comment-13047357
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. Would the rowkey and columnkey be automatically included in the result
Yes, appropriately aliased, when doing a wildcard SELECT. Otherwise only
columns (or aliases) explicitly requested should be included. In other words,
you would get the above result either with "SELECT *" or "SELECT rowkey,
columnkey, subcol1, subcol2" but "SELECT subcol1, subcol2" would only give the
requested columns (and "SELECT rowkey, subcol1, subcol2" would also be
honored).
In short, we minimize "magic" and don't assume we know better than the query
author ("you didn't request the row key but I'm going to stick it in your
resultset anyway").
bq. Is that a proposal for CQL?
I'd view it as not nearly as important as the single-row case but I'm not
against it.
> 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
