public interface TransactionChain extends org.opendaylight.yangtools.concepts.Registration, TransactionFactory
AsyncWriteTransaction t1 = broker.newWriteOnlyTransaction();
t1.put(id, data);
t1.commit();
AsyncReadTransaction t2 = broker.newReadOnlyTransaction();
Optional<?> maybeData = t2.read(id).get();
it may happen, that it sees maybeData.isPresent() == false, simply because t1 has not completed the processes
of being applied and t2 is actually allocated from the previous state. This is obviously bad for users who create
incremental state in the datastore and actually read what they write in subsequent transactions. Using
a TransactionChain instead of a broker solves this particular problem, and leads to expected behavior: t2 will always
see the data written in t1 present.| Modifier and Type | Method and Description |
|---|---|
ReadTransaction |
newReadOnlyTransaction()
Create a new read only transaction which will continue the chain.
|
ReadWriteTransaction |
newReadWriteTransaction()
Create a new read-write transaction which will continue the chain.
|
WriteTransaction |
newWriteOnlyTransaction()
Create a new write-only transaction which will continue the chain.
|
ReadTransaction newReadOnlyTransaction()
The previous write transaction has to be either SUBMITTED (commit was invoked)
or CANCELLED (close was invoked).
The returned read-only transaction presents an isolated view of the data if the previous write transaction was successful - in other words, this read-only transaction will see the state changes made by the previous write transaction in the chain. However, state which was introduced by other transactions outside this transaction chain after creation of the previous transaction is not visible.
newReadOnlyTransaction in interface TransactionFactoryIllegalStateException - if the previous transaction was not SUBMITTED or CANCELLED.TransactionChainClosedException - if the chain has been closed.WriteTransaction newWriteOnlyTransaction()
The previous write transaction has to be either SUBMITTED (commit was invoked)
or CANCELLED (close was invoked)
The returned write-only transaction presents an isolated view of the data if the previous write transaction was successful - in other words, this write-only transaction will see the state changes made by the previous write transaction in the chain. However, state which was introduced by other transactions outside this transaction chain after creation of the previous transaction is not visible
Committing this write-only transaction using commit will commit the state
changes in this transaction to be visible to any subsequent transaction in this chain and also to any transaction
outside this chain.
newWriteOnlyTransaction in interface TransactionFactoryIllegalStateException - if the previous transaction was not SUBMITTED or CANCELLED.TransactionChainClosedException - if the chain has been closed.ReadWriteTransaction newReadWriteTransaction()
The previous write transaction has to be either SUBMITTED (commit was invoked)
or CANCELLED (close was invoked).
The returned read-write transaction presents an isolated view of the data if the previous write transaction was successful - in other words, this read-write transaction will see the state changes made by the previous write transaction in the chain. However, state which was introduced by other transactions outside this transaction chain after creation of the previous transaction is not visible.
Committing this read-write transaction using commit will commit the state changes
in this transaction to be visible to any subsequent transaction in this chain and also to any transaction outside
this chain.
newReadWriteTransaction in interface TransactionFactoryIllegalStateException - if the previous transaction was not SUBMITTED or CANCELLED.TransactionChainClosedException - if the chain has been closed.Copyright © 2019 OpenDaylight. All rights reserved.