<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:37 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[YANGTOOLS-899] Unify NodeIdentifier and NodeIdentifierWithPredicates</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-899</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;The dichotomy of these two PathArguments leads to keyed list items being addressed through two PathArguments. With &lt;del&gt;&lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-585&quot; title=&quot;Data tree: automatic structural lifecycle&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-585&quot;&gt;&lt;del&gt;YANGTOOLS-585&lt;/del&gt;&lt;/a&gt;&lt;/del&gt; out of the way the presence of lists as&#160; DataTree elements is an implementation detail, as they are completely transparent to datastore operations.&lt;/p&gt;

&lt;p&gt;Considering filtering requirements coming from RFC6241, there really are four levels of NodeIdentifier when we are considering lists:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;NodeIdentifier: select all members&lt;/li&gt;
	&lt;li&gt;NodeIdentifierWithPredicates: select a single (keyed) list entry&lt;/li&gt;
	&lt;li&gt;NodeIdentifier + NodePredicates: select all nodes matching predicates&lt;/li&gt;
	&lt;li&gt;if NodePredicates is a superset of key predicates: select single entry if it is matching additional predicates&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;This has interplay with other types like containers, where predicates must match leaves &#8211; hence having a read() of a container using NodeIdentifier + NodePredicates would a well-defined filtering operation. We also need to consider implementation complexity and usefulness in face of the fact we want to support XPath queries at some point.&lt;/p&gt;</description>
                <environment></environment>
        <key id="30652">YANGTOOLS-899</key>
            <summary>Unify NodeIdentifier and NodeIdentifierWithPredicates</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <status id="10003" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Confirmed</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="rovarga">Robert Varga</reporter>
                        <labels>
                    </labels>
                <created>Mon, 27 Aug 2018 23:46:50 +0000</created>
                <updated>Fri, 5 Jan 2024 14:53:57 +0000</updated>
                                                            <fixVersion>14.0.0</fixVersion>
                                    <component>data-impl</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="64863" author="rovarga" created="Mon, 3 Sep 2018 10:19:30 +0000"  >&lt;p&gt;While this issue deals with lists, where NodeIdentifierWithPredicates selects a certain list member, &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-568&quot; title=&quot;Remove AugmentationIdentifier and AugmentationNode&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-568&quot;&gt;&lt;del&gt;YANGTOOLS-568&lt;/del&gt;&lt;/a&gt; is geared towards elimination of AugmentationIdentifier &#8211; which instead becomes a child selection filter.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10003">
                    <name>Relates</name>
                                            <outwardlinks description="relates to">
                                        <issuelink>
            <issuekey id="22988">YANGTOOLS-568</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10002" key="com.pyxis.greenhopper.jira:gh-epic-link">
                        <customfieldname>Epic Link</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>YANGTOOLS-1022</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03i7z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>