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/03/02 17:49:40 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=13001480#comment-13001480 ] 

Ed Anuff edited comment on CASSANDRA-2233 at 3/2/11 4:49 PM:
-------------------------------------------------------------

Yes, I would think so.

Caveat: deprecate == not recommend for new usage, existing column families using the LexicalUUID have to stay with it, for the reason Frank points out.

      was (Author: edanuff):
    Yes, I would think so.
  
> 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: UUIDType.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