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/YANGTOOLS-738 yangtools <p>Since a SchemaContext is an immutable entity containing children which get referenced a lot, it would nice to have a really quick identifier unique within a SchemaContext instance.</p> <p>We have implemented something similar for declared statements in yang-parser-impl by each substatement track the (int) offset in which it appears in its parent.</p> <p>This allows quick lookups in the form of /2/7/0/1 to express the SchemaPath within a SchemaContext &#8211; extremely useful when there is some schema-specific state being tracked.</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-738

SchemaContext: unique SchemaNodeidentifiers

Improvement Resolved Won't Do Robert Varga Robert Varga Fri, 20 Jan 2017 01:39:30 +0000 Sun, 10 Apr 2022 18:35:57 +0000 Tue, 11 Feb 2020 16:17:58 +0000 0 3 <p>This is a bit more complex, and should not really be done in the context of SchemaNodes, but rather in EffectiveStatements.</p> <p>The identifier needs to understand how exactly the node is being identifier: is it via data tree or schema tree?</p> <p>This boils down to a StatementIdentifier and it should work solely on the statement tree, irrespective of data/schema trees.</p> <p>I am not sure how useful this is. In most contexts where we would lookup a SchemaNode/EffectiveStatement we should really have a stack of SchemaNode/EffectiveStatements with the topmost element being the one that is being resolved. This is used for example in leafref resolution, where we have relative paths involving parent steps – with such a stack we can accurately follow what is going on.</p> <p>So this really is only useful in serialization scenarios – in which case that would be a function of the 'statement stack' class.</p> <p>Maintaining this identifier is actually a reference to parent, as for example statements created by 'uses' can have the entire definition shared in a particular namespace (most probably), but they would end up needing to differ in this int – which can be addressed by flyweight objects, but it feels like an unnecessary complication.</p> <p>This issue runs against <a href="https://jira.opendaylight.org/browse/YANGTOOLS-1066" class="external-link" rel="nofollow">https://jira.opendaylight.org/browse/YANGTOOLS-1066</a> deliverables and would prevent us from sharing SchemaNode instances, closing it down.</p> Blocks YANGTOOLS-853 Relates YANGTOOLS-843 Development External issue ID 7605 External issue URL Issue Type ODL SR Target Milestone Rank 0|i0292v: