cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CASSANDRA-7919) Change timestamp representation to timeuuid
Date Sat, 13 Sep 2014 04:10:34 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132516#comment-14132516
] 

Benedict edited comment on CASSANDRA-7919 at 9/13/14 4:09 AM:
--------------------------------------------------------------

We can have multiple clients per interface (esp. cross DC, as could have multiple DCs with
the same network address range that do not communicate directly, but communicate with a shared
C* data centre), we can have multiple clients starts/stop at the same time. C* instances can
pretty much guarantee this doesn't happen; clients cannot. Once we have a collision on the
LSB, we are exposed indefinitely to conflicts.


was (Author: benedict):
We can have multiple clients per interface, we can have multiple clients starts/stop at the
same time. C* instances can pretty much guarantee this doesn't happen; clients cannot. Once
we have a collision on the LSB, we are exposed indefinitely to conflicts.

> 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)

Mime
View raw message