[
https://issues.apache.org/jira/browse/CASSANDRA-4329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13406435#comment-13406435
]
Pavel Yaskevich commented on CASSANDRA-4329:
--------------------------------------------
+1 with nit - instead of "system" in systemTableQuery(...) would be better to
use Table.SYSTEM_TABLE
> CQL3: Always use composite types by default
> --------------------------------------------
>
> Key: CASSANDRA-4329
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4329
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.2
>
> Attachments: 4329.txt, 4329_fix.txt
>
>
> Currently, when defining a table with a single (non-composite) PRIMARY KEY,
> we don't use a CompositeType in the underlying comparator. This is however a
> problem for CASSANDRA-3647 as this means those tables cannot use collections.
> So this ticket suggests to change that default behavior, and to always use
> (by default at least, see below) a composite comparator underneath. I'll note
> that doing so will mean an overhead of 3 bytes per column for non-composite
> columns, but I believe getting collection is well worth it.
> Of course the suggestion above apply to the default behavior and this ticket
> would also add an option to table creation to get back to the current
> behavior of not using a composite comparator (if ony for backward
> compatibility sake). And I believe that we can actually reuse 'COMPACT
> STORAGE' for that.
--
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
