org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.mdsaltrace.rev160908

Interface Config

All Superinterfaces:

Augmentable<Config>, BindingObject, ChildOf<MdsaltraceData>, DataContainer, DataObject

public interface Config
extends ChildOf<MdsaltraceData>, Augmentable<Config>

This class represents the following YANG schema fragment defined in module mdsaltrace

 container config {
   leaf-list registration-watches {
     type string;
   }
   leaf-list write-watches {
     type string;
   }
   leaf transaction-debug-context-enabled {
     default false;
     type boolean;
   }
 }
 

The schema path to identify an instance is mdsaltrace/config

To create instances of this class use ConfigBuilder.

See Also:

ConfigBuilder

Field Summary

Fields

Modifier and Type	Field and Description
static org.opendaylight.yangtools.yang.common.QName	QNAME

Method Summary

Modifier and Type	Method and Description
@Nullable List<String>	getRegistrationWatches()
@Nullable List<String>	getWriteWatches()
@Nullable Boolean	isTransactionDebugContextEnabled() Enable or disable transaction context debug.

Methods inherited from interface org.opendaylight.yangtools.yang.binding.DataContainer

getImplementedInterface

Methods inherited from interface org.opendaylight.yangtools.yang.binding.Augmentable

augmentation

Field Detail

QNAME

static final org.opendaylight.yangtools.yang.common.QName QNAME

Method Detail

getRegistrationWatches

@Nullable List<String> getRegistrationWatches()

Returns:

java.util.List registrationWatches, or null if not present

getWriteWatches

@Nullable List<String> getWriteWatches()

Returns:

java.util.List writeWatches, or null if not present

isTransactionDebugContextEnabled

@Nullable Boolean isTransactionDebugContextEnabled()

Enable or disable transaction context debug. This will preserve the call site trace fortransactions, so that the original caller of un-close'd() transaction can be identified.NB: This is a different property from the equally named one in etc/org.opendaylight.controller.cluster.datastore.cfg;that one does something somewhat similar, but serves to include the stack trace on failed transaction submit,whereas this one is specific to odl-mdsal-trace's trace:transaction leak troubleshooting command.

Returns:

java.lang.Boolean transactionDebugContextEnabled, or null if not present