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-620 yangtools <p>Union values are a nasty beast, as they are polymorphic and do not really have a native type. RFC6020(bis) maps their type to the first conforming member, which means each time we want to instantiate a union DTO (in Java Bindings, but this is not specific to them), we have to check each possibility until we find a match. This is especially troublesome unions of exotic types like binary, where the cost of getting the common representation cost quite a few CPU cycles.</p> <p>Introduce a dedicated value class for use with union types, which aside from the value in native type will hold the SchemaPath of the type being stored. It needs to be exposed as an Optional&lt;SchemaPath&gt; for compatibility with schema-less producers.</p> <p>This would probably be also beneficial for String types, where we get it trouble with Binding subclasses.</p> <p>Operating System: All<br/> Platform: All</p> YANGTOOLS-620

yang-model-api: define a structured type for union values

New Feature Confirmed Unresolved Unassigned Robert Varga Thu, 9 Jun 2016 00:03:08 +0000 Sun, 10 Apr 2022 18:35:47 +0000 0 2 <p><a href="https://jira.opendaylight.org/browse/YANGTOOLS-675" title="[Yang 1.1] Allow type &quot;leafref&quot; in unions" class="issue-link" data-issue-key="YANGTOOLS-675">YANGTOOLS-675</a> will need this structured information to reinterpret unions during datastore operations.</p> <p>Punting this to 4.0.0, because the proposed design will not work. The problem is that members within a union cannot be reliably addressed through SchemaPath, for example in this case:</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-java"> union foo { type string { pattern <span class="code-quote">"a"</span>; } type string { pattern <span class="code-quote">"b"</span>; } type union { type uint8t; } } </pre> </div></div> <p>Furthermore SchemaPath is a yang-model-api, whereas we need to identify the types in terms of yang-common. We could go with simple integers, but we probably also want some amount of support from the parser, i.e. similar to CanonicalValue.</p> Blocks YANGTOOLS-675 Development External issue ID 6032 External issue URL Issue Type Rank 0|i028cn: