Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <13083097.183701284483995125.JavaMail.jira@thor>
Date: Tue, 14 Sep 2010 13:06:35 -0400 (EDT)
From: "Johan Oskarsson (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1501) remove Clock from Thrift API
In-Reply-To: <15513039.181411284478714039.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Johan Oskarsson commented on CASSANDRA-1501:
--------------------------------------------

We still need a way to differentiate between timestamp and increment counter in CASSANDRA-1072. The easiest way would be to just leave the clock internals in place. In this patch we'd still need clock_type and reconciler.
A minor detail is that the timestamp variable is still called clock in the patch.

> remove Clock from Thrift API
> ----------------------------
>
>                 Key: CASSANDRA-1501
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1501
>             Project: Cassandra
>          Issue Type: Task
>          Components: API
>    Affects Versions: 0.7 beta 1
>            Reporter: Jonathan Ellis
>            Assignee: Jonathan Ellis
>             Fix For: 0.7 beta 2
>
>         Attachments: 1501.txt
>
>
> Clock was introduced back when we insufficiently understood the limitations of CASSANDRA-580. It turns out to not be necessary. This ticket removes it from the Thrift API to get ready for 0.7.0; removing it from the rest of the internals can follow.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.