Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 17 Mar 2015 15:03:39 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12765085.1420538204000.117844.1426604619353@Atlassian.JIRA>
In-Reply-To: <JIRA.12765085.1420538204000@Atlassian.JIRA>
References: <JIRA.12765085.1420538204000@Atlassian.JIRA>
 <JIRA.12765085.1420538204272@arcas>
Subject: [jira] [Commented] (CASSANDRA-8568) Impose new API on data tracker
 modifications that makes correct usage obvious and imposes safety
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-8568:
-------------------------------------------

SGTM.

> Impose new API on data tracker modifications that makes correct usage obvious and imposes safety
> ------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-8568
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8568
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Benedict
>            Assignee: Benedict
>
> DataTracker has become a bit of a quagmire, and not at all obvious to interface with, with many subtly different modifiers. I suspect it is still subtly broken, especially around error recovery.
> I propose piggy-backing on CASSANDRA-7705 to offer RAII (and GC-enforced, for those situations where a try/finally block isn't possible) objects that have transactional behaviour, and with few simple declarative methods that can be composed simply to provide all of the functionality we currently need.
> See CASSANDRA-8399 for context


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)