cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-2233) Add unified UUIDType
Date Sat, 09 Apr 2011 21:57:05 GMT


Jonathan Ellis updated CASSANDRA-2233:

    Attachment: 2233.txt

rebased and changed testCompare to only care about version 1 results, and validate against
TimeUUIDType, but I'm getting a failure:

    [junit] Testcase: testCompare(org.apache.cassandra.db.marshal.UUIDTypeTest):	FAILED
    [junit] expected:<-1> but was:<-23>
    [junit] junit.framework.AssertionFailedError: expected:<-1> but was:<-23>
    [junit] 	at org.apache.cassandra.db.marshal.UUIDTypeTest.testCompare(
    [junit] 	at org.apache.cassandra.db.marshal.UUIDTypeTest.testCompare(


> Add unified UUIDType
> --------------------
>                 Key: CASSANDRA-2233
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.3
>            Reporter: Ed Anuff
>            Priority: Minor
>         Attachments: 2233.txt,,
> Unified UUIDType comparator, compares as time-based if both UUIDs are time-based, otherwise
uses byte comparison.  Based on code from the current LexicalUUIDType and TimeUUIDType comparers,
so performance and behavior should be consistent and compatible.

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

View raw message