[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185200#comment-13185200
]
paul cannon commented on CASSANDRA-2474:
----------------------------------------
bq. I'll also note that this patch (with the things above) make it so that in
the CqlMetadata (in the result), the name_types are not useful anymore (since
this is always UTF8), and neither is the default comparator and default
validation types, as we can always set the type of each columns in the
value_types map. I suppose the best way to proceed is to mark them deprecated
for now and remove them in the next version.
This seems possibly too far. Clients ought to be able to know what a CF's
default comparator and validation types are, even if they're not necessary to
deserialize column values.
Also, cqlsh has an ASSUME facility similar to the cli one. You can tell cqlsh
to deserialize columns without an explicit column type as though they were
something different. Would this still be possible without being able to tell
whether column values had an explicit column_metadata type, or whether they
were using the default?
> CQL support for compound columns and wide rows
> ----------------------------------------------
>
> 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: Sylvain Lebresne
> Priority: Critical
> 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,
> cql_tests.py, 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
