[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13176455#comment-13176455
]
Matt Stump commented on CASSANDRA-2474:
---------------------------------------
I wanted to bring this up because it hasn't been mentioned yet, and it's
currently a topic of discussion on the hector-users list: for query results of
composite columns are you going to deserialize the column name or leave it as
an opaque blob? For the current implementation of composite columns in Hector
the type information for dynamic composites is encoded in the name, but that
information is lacking for the static variety. My understanding is that the
type information is only stored at the CFDef level as the type alias, and could
possibly be cached to aide in deserialization but that seems like a bit of a
hack.
> 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
