cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate McCall (Commented) (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3657) Allow extending CompositeType comparator
Date Tue, 24 Jan 2012 18:46:40 GMT


Nate McCall commented on CASSANDRA-3657:

After modifying the column family (for posterity, I'm going to state here that you do need
to modify the comparator declaration to "extend" it) with the above command on the cli:

update column family CountryStateCity with comparator = 'CompositeType(UTF8Type,UTF8Type,UTF8Type,LongType)';

Inserts of three and four values from Hector both work correctly (where the fourth value is
a LongType of course). 

All unit tests pass, so LGTM. 
> Allow extending CompositeType comparator
> ----------------------------------------
>                 Key: CASSANDRA-3657
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>    Affects Versions: 0.8.1
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>            Priority: Critical
>             Fix For: 1.1
>         Attachments: 0001-Allow-compatible-comparator-changes-v2.patch, 0001-Allow-compatible-comparator-changes.patch
> Quoting Sylvain from CASSANDRA-2474,
> bq. if you declare a comparator like CompositeType(IntType, UUIDType, UTF8Type), you
can have columns that have only some prefix of the component (typically '42:92d21d0a-d6cb-437c-9d3f-b67aa733a19f'
is a valid column name for that comparator), and as a consequence it would be possible to
allow 'extend' the preceding comparator to say CompositeType(IntType, UUIDType, UTF8Type,

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