[ https://issues.apache.org/jira/browse/CASSANDRA-8568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benedict updated CASSANDRA-8568: -------------------------------- Summary: Extend Transactional API to sstable lifecycle management (was: Impose new API on data tracker modifications that makes correct usage obvious and imposes safety) > Extend Transactional API to sstable lifecycle management > -------------------------------------------------------- > > Key: CASSANDRA-8568 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8568 > Project: Cassandra > Issue Type: Bug > Reporter: Benedict > Assignee: Benedict > Fix For: 2.2.0 rc1 > > > 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)