cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (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 Tue, 28 Apr 2015 16:12:06 GMT

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

Benedict commented on CASSANDRA-8568:
-------------------------------------

[~krummas]: I've rebased against 8984-alt and force pushed. There are some failing unit tests
but these are all broken against trunk, and appear to be due to embedded Cassandra and singletons.
I'll rebase again once they're fixed, but since 8984-alt is agreed except for testing you
should be good to begin review at your leisure.

> 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