[
https://issues.apache.org/jira/browse/CASSANDRA-8730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14311330#comment-14311330
]
Benedict commented on CASSANDRA-8730:
-------------------------------------
Uploaded a new version that makes TimeUUIDType extend UUIDType, since I don't
think the handful of cycles we might save with specialisation warrant the
icache pollution, and future idiots like me won't make the mistake when
updating one and not the other :)
At the same time, I merged the fromString() behaviour to make it a bit cleaner,
and in doing so noticed that the behaviour isn't consistent between the two for
date-string provision. It looks to me like TimeUUID had the behaviour
downgraded to CQL2 only, whereas UUID has not. I wonder if this was down to
somebody else making the same mistake I did, only in reverse. [~slebresne]
[~thobbs] - as CQL experts, could you enlighten on this?
> Optimize UUIDType comparisons
> -----------------------------
>
> Key: CASSANDRA-8730
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8730
> Project: Cassandra
> Issue Type: Improvement
> Reporter: J.B. Langston
> Assignee: Benedict
> Fix For: 2.1.4
>
>
> Compaction is slow on tables using compound keys containing UUIDs due to
> being CPU bound by key comparison. [~benedict] said he sees some easy
> optimizations that could be made for UUID comparison.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
