Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sat, 13 Sep 2014 21:48:34 +0000 (UTC)
From: "Sylvain Lebresne (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12741193.1410561707000.28825.1410644914466@Atlassian.JIRA>
In-Reply-To: <JIRA.12741193.1410561707000@Atlassian.JIRA>
References: <JIRA.12741193.1410561707000@Atlassian.JIRA>
 <JIRA.12741193.1410561707305@arcas>
Subject: [jira] [Commented] (CASSANDRA-7919) Change timestamp representation
 to timeuuid
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Sylvain Lebresne commented on CASSANDRA-7919:
---------------------------------------------

bq. This is not true if we incorporate CASSANDRA-7925

I don't see how CASSANDRA-7925 changes that really. When I say client, I mean process. You can have multiple client/process on one box, but that don't change the fact that a given client process will have one lsb for its lifetime.

bq. we should not deliver the TimeUUID back to clients, and we should not store it fully indefinitely

I don't have a problem with that.

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