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-102 mdsal <p>These statements need to be enforced.</p> <p>Operating System: All<br/> Platform: All</p> MDSAL-102

YANG 'default' statements is not being enforced

Improvement Resolved Done Robert Varga Jan Medved Wed, 16 Sep 2015 14:09:22 +0000 Fri, 9 Mar 2018 18:00:10 +0000 Tue, 17 Nov 2015 18:22:56 +0000 0 1 <p>I split off BUG-4355 to track mandatory statement enforcement.</p> <p><a href="https://tools.ietf.org/html/rfc6020#section-7.6.4" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc6020#section-7.6.4</a> does not define any enforcement rules. There is a definition of system behavior in <a href="https://tools.ietf.org/html/rfc6020#section-7.6.1" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc6020#section-7.6.1</a>, but that behavior can be realized in multiple ways, which achieve slightly different results.</p> <p>One would be instantiating nodes as they are written into the data store, but that has the unfortunate effect of those nodes being actually there &#8211; e.g. RESTCONF would see those nodes present even when they have not been actually provisioned.</p> <p>Another approach would be to instantiate default-valued nodes when they are explictly queried for via NormalizedNodeContainer.getChild(), but not through NormalizedNodeContainer.getValue().iterator(), but that would require normalized nodes to have the underlying SchemaNode available or carry an optional map of default values.</p> <p>Yet another approach would be realized when the nodes is accessed in the context of a Data Tree instance via DataTreeSnapshot.read() or within implementation internal access (such as 'when' statement enforcement).</p> <p>If this functionality is needed only in the BA world, this behavior can be implemented in generated code without affecting BI at all.</p> <p>A default statement determines a value that should be filled into an optional attribute if the user does not specify the attribute. (Note that default does not make a lot of sense for mandatory attributes, but we're not enforcing those either - so by implementing 'default' we need to implement 'mandatory' as well)</p> <p>This allows simplified processing, because the implementor can assume that the attribute is never null and/or does not have to write code to fill the default value.</p> <p>The best option here would be change the behavior of LazyDataObject to return default value when asked for it.</p> <p>This will result in any data reported to Binding Aware users as being set to the default value, while not storing it in the Binding Independent part of the world.</p> <p>This behavior should be OK for BI users, as they usually have access to SchemaContext, where they acquire the default value (just as LazyDataObject, which is a BI component).</p> <p><a href="https://git.opendaylight.org/gerrit/28251" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/28251</a></p> Development External issue ID 4322 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02wbr: