You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "paul cannon (JIRA)" <ji...@apache.org> on 2012/08/05 07:05:03 UTC
[jira] [Updated] (CASSANDRA-3647) Support collection (list, set,
and map) value types in CQL
[ https://issues.apache.org/jira/browse/CASSANDRA-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
paul cannon updated CASSANDRA-3647:
-----------------------------------
Attachment: 3647-nit.txt
Just a small thing that would make cqlsh's life a little easier in trying to make sense of the 'comparator' field in system.schema_columnfamilies. The formatting in TypeParser.stringifyCollectionParameters is a bit backwards.
Don't think this justifies a reopen.
> Support collection (list, set, and map) value types in CQL
> ----------------------------------------------------------
>
> Key: CASSANDRA-3647
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3647
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Sylvain Lebresne
> Labels: cql
> Fix For: 1.2
>
> Attachments: 3647-nit.txt, CASSANDRA-3647-alternative.patch
>
>
> Composite columns introduce the ability to have arbitrarily nested data in a Cassandra row. We should expose this through CQL.
--
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