<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:54:10 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-741] Improve a substatement context lookup in yang statement parser</title>
                <link>https://jira.opendaylight.org/browse/YANGTOOLS-741</link>
                <project id="10188" key="YANGTOOLS">yangtools</project>
                    <description>&lt;p&gt;Very often we need to check whether a substatement with a specific statement definition exists under some statement context in yang statement parser or to look up a substatement (or substatements) with a specific statement definition. &lt;/p&gt;

&lt;p&gt;Currently, in order to do that we need to iterate over all current context&apos;s substatements and check whether there is a substatement we are looking for.&lt;/p&gt;

&lt;p&gt;I think using a MultiMap keyed by StatementDefinition instead of List for substatement contexts will improve these lookups significantly.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="23161">YANGTOOLS-741</key>
            <summary>Improve a substatement context lookup in yang statement parser</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="1" iconUrl="https://jira.opendaylight.org/images/icons/priorities/blocker.svg">Highest</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="pkajsa">Peter Kajsa</reporter>
                        <labels>
                    </labels>
                <created>Thu, 2 Feb 2017 09:42:20 +0000</created>
                <updated>Fri, 30 Oct 2020 13:37:36 +0000</updated>
                            <resolved>Tue, 12 Jun 2018 13:26:43 +0000</resolved>
                                                                    <component>parser</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="44324" author="rovarga" created="Sun, 5 Mar 2017 14:33:40 +0000"  >&lt;p&gt;Nitrogen planning has not begun, hence de-targetting this one.&lt;/p&gt;</comment>
                            <comment id="44325" author="rovarga" created="Thu, 24 Aug 2017 13:34:02 +0000"  >&lt;p&gt;We cannot use MultiMap, as we need to retain order of definition (hence substatements needs to still be indexed using an integer). It could be a secondary index, but we need to solve &lt;a href=&quot;https://jira.opendaylight.org/browse/YANGTOOLS-694&quot; title=&quot;Eliminate duplicate DescriptionEffectiveStatementImpl objects&quot; class=&quot;issue-link&quot; data-issue-key=&quot;YANGTOOLS-694&quot;&gt;&lt;del&gt;YANGTOOLS-694&lt;/del&gt;&lt;/a&gt; otherwise our memory usage will explode.&lt;/p&gt;

&lt;p&gt;A further thought, though: we need a detailed analysis of what is the actual iteration cost, since I suspect most of the time we have only a few substatements &amp;#8211; hence linear lookups are not that bad.&lt;/p&gt;</comment>
                            <comment id="63411" author="rovarga" created="Tue, 12 Jun 2018 13:26:43 +0000"  >&lt;p&gt;I don&apos;t think this is really needed.&lt;/p&gt;</comment>
                    </comments>
                    <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-652</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>7726</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=7726]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10305"><![CDATA[Improvement]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i0293j:</customfieldvalue>

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