cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2231) Add CompositeType comparer to the comparers provided in org.apache.cassandra.db.marshal
Date Thu, 14 Apr 2011 13:52:06 GMT


Sylvain Lebresne updated CASSANDRA-2231:

    Attachment: 0001-Add-compositeType-and-DynamicCompositeType-v2.patch

Rebased and updated patch attached. The new patch use -1, 0, 1 for the end-of-component. It
also fixes some issue I add fixed in CASSANDRA-2355 but really belong here, namely handling
the parameters of the composite types when deflating CFMetadata into Avro, etc...

This still a patch against 0.7. I think this is really not very disruptive and could go into
0.7, but I can rebase to 0.8 otherwise. The only problem I can think of is if someone already
have a custom comparator named CompositeType or DynamicCompositeType, but that's a problem
we face each time we add a new comparator.

> Add CompositeType comparer to the comparers provided in org.apache.cassandra.db.marshal
> ---------------------------------------------------------------------------------------
>                 Key: CASSANDRA-2231
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Contrib
>    Affects Versions: 0.7.3
>            Reporter: Ed Anuff
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 0.7.5
>         Attachments: 0001-Add-compositeType-and-DynamicCompositeType-v2.patch, CompositeType-and-DynamicCompositeType.patch,
> CompositeType is a custom comparer that makes it possible to create comparable composite
values out of the basic types that Cassandra currently supports, such as Long, UUID, etc.
 This is very useful in both the creation of custom inverted indexes using columns in a skinny
row, where each column name is a composite value, and also when using Cassandra's built-in
secondary index support, where it can be used to encode the values in the columns that Cassandra
indexes.  One scenario for the usage of these is documented here:
 Source for contribution is attached and has been previously maintained on github here:

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message