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 16:42:41 GMT


Nate McCall commented on CASSANDRA-3657:

Comparison works via the unit tests, but it looks like validation does not. 

Given a column family with the following definition:
create column family CountryStateCity
with comparator = 'CompositeType(UTF8Type,UTF8Type,UTF8Type)'
and key_validation_class = 'UTF8Type'
and default_validation_class = 'UTF8Type';

Inserting data with a Composite structured like the following causes a validation error from

> 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.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