[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173480#comment-13173480
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. I didn't though the goal was to 'adapt to the relational philosophy'
All data is relational, the only question is implementation details. :)
Seriously though, "send a query, get back rows" is a good design for a language
+ driver, and you simply can't represent slices of wide, composite rows sanely
that way without something like transposition to expose the structure "hidden"
underneath.
bq. WITH comparator = composite(sender,thread,tid);
Wouldn't you need body in the composite list too?
bq. --Finally in the case of both SPARSE/DENSE
So this is basically what I gave, right? It sounds like you're bikeshedding
the TRANSPOSED / WITH COMPARATOR syntax but not really solving the problem I
outlined. Maybe I'm missing something.
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Pavel Yaskevich
> Labels: cql
> Fix For: 1.1
>
> Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG,
> 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG,
> raw_composite.txt, 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
