[ https://issues.apache.org/jira/browse/CASSANDRA-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132487#comment-14132487 ]
Benedict commented on CASSANDRA-7919: ------------------------------------- See my comments on CASSANDRA-6108 for details of why I don't think this is suitable. Since we specifically want this for RAMP transactions we need guaranteed uniqueness cross-cluster, which timeuuids only achieve if created _server side_. We will absolutely have to modify the semantics of TimeUUID if we want them to be guaranteed unique still, at which point we may as well consider the 64-bit representation I suggested on that ticket. > Change timestamp representation to timeuuid > ------------------------------------------- > > Key: CASSANDRA-7919 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7919 > Project: Cassandra > Issue Type: Improvement > Reporter: T Jake Luciani > Priority: Minor > Fix For: 3.0 > > > In order to overcome some of the issues with timestamps (CASSANDRA-6123) we > need to migrate to a better timestamp representation for cells. > Since drivers already support timeuuid it makes sense to migrate to this > internally (see CASSANDRA-7056) -- This message was sent by Atlassian JIRA (v6.3.4#6332)