[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13098198#comment-13098198
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. I guess what I'm arguing here is just to not forget the case where you use
CompositeType because your column key do is intrinsically composed of multiple
parts
I think something got lost along the way here, because I've been very clear
from the beginning that we do need to support the "dense" case, and that I
prefer "the component syntax" in part because it does accommodate that. We can
bikeshed all day about whether "sparse" or "dense" is the more common, but
bottom line is we need to support both.
> 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
