cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-8568) Impose new API on data tracker modifications that makes correct usage obvious and imposes safety
Date Wed, 18 Mar 2015 02:41:38 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-8568:
--------------------------------------
    Reviewer: Marcus Eriksson

(I assigned Josh to review 8984 and Marcus this one, under the assumption that they can be
done in parallel.  If not, let's give both to Marcus.)

> 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
>             Fix For: 3.0
>
>
> 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)

Mime
View raw message