[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099088#comment-13099088
]
Sylvain Lebresne commented on CASSANDRA-2474:
---------------------------------------------
bq. because I've been very clear from the beginning that we do need to support
the "dense" case
Alright, cool.
bq. We can bikeshed all day about whether "sparse" or "dense" is the more
common, but bottom line is we need to support both
Agreed. I just felt from the conversation that "dense" was getting really much
less love that sparse based on the argument that "doing dense is wrong". Since
I disagree with that argument, I just wanted to make sure we don't pick a
syntax that discourage "dense" too much (again, which isn't saying we should
discourage "sparse" either).
One thing I hadn't followed at first was that we planned to deprecate the '..'
notation in favor for transposed view even for non-composite columns. But now
that I've connected the dots, that makes sense.
> 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
