public class ShardedDOMReadWriteTransactionAdapter extends ShardedDOMWriteTransactionAdapter implements DOMDataTreeReadWriteTransaction
Modifier and Type | Method and Description |
---|---|
boolean |
cancel()
Cancels the transaction.
|
com.google.common.util.concurrent.FluentFuture<Boolean> |
exists(LogicalDatastoreType store,
org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier path)
Checks if data is available in the logical data store located at provided path.
|
com.google.common.util.concurrent.FluentFuture<Optional<org.opendaylight.yangtools.yang.data.api.schema.NormalizedNode<?,?>>> |
read(LogicalDatastoreType store,
org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier path)
Reads data from provided logical data store located at the provided path.
|
commit, delete, getIdentifier, merge, put
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
close
commit
delete, merge, put
public com.google.common.util.concurrent.FluentFuture<Optional<org.opendaylight.yangtools.yang.data.api.schema.NormalizedNode<?,?>>> read(LogicalDatastoreType store, org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier path)
DOMDataTreeReadOperations
If the target is a subtree, then the whole subtree is read (and will be accessible from the returned data object).
read
in interface DOMDataTreeReadOperations
store
- Logical data store from which read should occur.path
- Path which uniquely identifies subtree which client want to readReadFailedException
or
an exception derived from ReadFailedException.public com.google.common.util.concurrent.FluentFuture<Boolean> exists(LogicalDatastoreType store, org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier path)
DOMDataTreeReadOperations
Note: a successful result from this method makes no guarantee that a subsequent call to DOMDataTreeReadOperations.read(org.opendaylight.mdsal.common.api.LogicalDatastoreType, org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier)
will
succeed. It is possible that the data resides in a data store on a remote node and, if that node goes down or
a network failure occurs, a subsequent read would fail. Another scenario is if the data is deleted in between
the calls to exists
and read
exists
in interface DOMDataTreeReadOperations
store
- Logical data store from which read should occur.path
- Path which uniquely identifies subtree which client want to check existence ofReadFailedException
or
an exception derived from ReadFailedException.public boolean cancel()
DOMDataTreeWriteTransaction
DOMDataTreeWriteTransaction.commit()
already successfully completed)
will always fail (return false).cancel
in interface DOMDataTreeWriteTransaction
cancel
in class ShardedDOMWriteTransactionAdapter
Copyright © 2019 OpenDaylight. All rights reserved.