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

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

Yep, I would agree with you 100% were it not for the recent problems. And I 
still lean in that direction, since this is a complex change. My concern is 
only if we haven't fully addressed the existing problems, because our testing 
as it stands doesn't seem able to elicit them. So anything that both improves 
testing and robustness in this area has a compelling reason for inclusion, if 
not a sufficient one.

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

Reply via email to