[
https://issues.apache.org/jira/browse/CASSANDRA-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000479#comment-13000479
]
Ed Anuff commented on CASSANDRA-2233:
-------------------------------------
This wasn't necessarily suggested as a replacement for the two existing
comparators but as an alternative for:
(1) convenience
(2) being able to switch your UUID generation technique later and while the
ordering might not be useful, it would still be predictable. What happens now
if you start with time-based UUIDs and switch to lexical?
(3) use foreign generated UUID's with a preference for time-based sorting if
possible
> 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
