[
https://issues.apache.org/jira/browse/CASSANDRA-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132807#comment-14132807
]
T Jake Luciani commented on CASSANDRA-7919:
-------------------------------------------
[~benedict] I was under the impression you were comfortable with this approach
because you said: "I am comfortable with that approach" :)
https://issues.apache.org/jira/browse/CASSANDRA-6108?focusedCommentId=14040659&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14040659
I think we can add enough entropy into the LSB to make this a very rare
possibility (as with all UUIDs). I think this is the best solution given all
clients need to support them and we already support timeuuid. In the file
format we can encode the timestamp separately (we already need to deal with
this issue for timeuuid columns anyway).
> 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)
