cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-2474) CQL support for compound columns and wide rows
Date Fri, 13 Jan 2012 09:45:40 GMT


Sylvain Lebresne commented on CASSANDRA-2474:

bq. In this situation, cqlsh should deserialize 'keyname' values as uuid, and 'username' values
as utf8, but any other column values should be deserialized as floa

I guess my point is that your example wouldn't be valid anymore after this patch (it may still
be accepted for one version for compatibility sake but that's all). And the ASSUME would look
ASSUME column_name IS type IN cf;

Of course, for a good part, this amount to my argument that static CF should be really static.
If we end up disagreeing with that (which would be a mistake but that's another point :D),
then yes, both the 'WITH default_validation' syntax for CREATE and the default_validator in
the CqlMetatada would have to stay (which is actually not a bad argument in favor of my proposal
of static is static IMHO).  But let's say that at least CqlMetadata.name_types and CqlMetadata.comparator
will lose their usefulness in any case.

> CQL support for compound columns and wide rows
> ----------------------------------------------
>                 Key: CASSANDRA-2474
>                 URL:
>             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,, 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:!default.jspa
For more information on JIRA, see:


View raw message