[
https://issues.apache.org/jira/browse/CASSANDRA-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132935#comment-14132935
]
Benedict commented on CASSANDRA-7919:
-------------------------------------
bq. Regarding the lsb, a given client shouldn't really change it during it's
lifetime (per the timeuuid spec)
This is not true if we incorporate CASSANDRA-7925
If we fix this, which we should, and we use TimeUUID for solving this problem
generally, we should _not_ deliver the TimeUUID back to clients, and we should
not store it fully indefinitely. We should only use it for guaranteeing
uniqueness, and after that truncate it to a simple timestamp. There is no
benefit to storing it indefinitely.
> 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)
