[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185301#comment-13185301
]
paul cannon commented on CASSANDRA-2474:
----------------------------------------
bq. I don't see any problem to having an ASSUME facility with what I'm
proposing. Maybe it will be more clear with the patch, but I really thing that
after the patch those info adds really no value to the resultSet.
Example:
{noformat}
CREATE COLUMNFAMILY columnfam (keyname uuid PRIMARY KEY, username utf8) WITH
default_validation = blob;
ASSUME columnfam VALUES ARE float;
{noformat}
In this situation, cqlsh should deserialize 'keyname' values as uuid, and
'username' values as utf8, but any other column values should be deserialized
as float. cqlsh currently makes the distinction by seeing whether the type for
a value is given in the CqlMetadata.value_types field. It sounds like your
proposal involves sending a type for every column in the result; am I
misinterpreting that?
I guess cqlsh could query the columnfamily options itself whenever it needed to
determine the default_validation, but that seems like it kind of makes
CqlMetadata useless.
> 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
