https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/MDSAL-61 mdsal <p>Current APIs exposes such future, but also submits transaction as side effect, but some use-cases shows, that having that future existing before transaction is submitted could potentially ease development of proper monitoring of transactions.</p> <p>This is also true for TypedTransactions, where the body being executed only sees ReadOperations/WriteOperations, hence cannot actually submit the future – but it may want to hook further processing based on the outcome of the transaction. Hence the future should really be exposed from *Operations interface.</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-61

Data Broker transactions should expose future which will complete when transaction is commited

Improvement Resolved Done Robert Varga Tony Tkacik Thu, 13 Nov 2014 13:04:43 +0000 Sun, 14 Jan 2024 14:54:00 +0000 Sun, 14 Jan 2024 14:54:00 +0000 13.0.0 Binding API DOM API 0 2 <p>Move to MDSAL.</p> <p>Furthermore transaction(chain) allocation should return a FluentFuture, so that implementations do not have to deal with the synchronous returns and users are guided towards event-driven programming.</p> <p>This would be a separate issue.</p> <p>The patch is quite risky as it involves changing future lifecycle. We already have enough risks going with datastore, let's punt his for a release.</p> Development External issue ID 2379 External issue URL Issue Type Rank 0|i02w2n: