cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-4329) CQL3: Always use composite types by default
Date Mon, 11 Jun 2012 12:23:42 GMT
Sylvain Lebresne created CASSANDRA-4329:
-------------------------------------------

             Summary: 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
             Fix For: 1.2


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

        

Mime
View raw message