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] [Commented] (CASSANDRA-8568) Impose new API on data tracker modifications that makes correct usage obvious and imposes safety
Date Mon, 16 Mar 2015 14:57:39 GMT

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

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

Can we get stability benefits in 2.1 by committing to 3.0 and backporting fixes as it exposes
problems?

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

Mime
View raw message