You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Ed Anuff (JIRA)" <ji...@apache.org> on 2011/04/10 00:09:05 UTC
[jira] [Issue Comment Edited] (CASSANDRA-2233) Add unified UUIDType
[ https://issues.apache.org/jira/browse/CASSANDRA-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13017969#comment-13017969 ]
Ed Anuff edited comment on CASSANDRA-2233 at 4/9/11 10:08 PM:
--------------------------------------------------------------
Hi Jonathan, thanks for testing it out. It's following the convention of [http://download.oracle.com/javase/6/docs/api/java/util/Comparator.html#compare%28T,%20T%29] to return a negative or positive value which is not necessarily -1 or +1. I can normalize it to those values if we want to hold to a tighter standard. What do you suggest?
Edit: Oops, just saw you added a sign() method to do that already.
was (Author: edanuff):
Hi Jonathan, thanks for testing it out. It's following the convention of [http://download.oracle.com/javase/6/docs/api/java/util/Comparator.html#compare%28T,%20T%29] to return a negative or positive value which is not necessarily -1 or +1. I can normalize it to those values if we want to hold to a tighter standard. What do you suggest?
> Add unified UUIDType
> --------------------
>
> Key: CASSANDRA-2233
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2233
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Affects Versions: 0.7.3
> Reporter: Ed Anuff
> Priority: Minor
> Attachments: 2233.txt, UUIDType.java, UUIDTypeTest.java
>
>
> 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: http://www.atlassian.com/software/jira