<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:55:45 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>[CONTROLLER-1517] Upgrading model leads to existing data in old model being flushed</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1517</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;I had a simple model included in my ODL run (within a model.jar having artifact version 0.1.0-SNAPSHOT). The model was as follows:&lt;/p&gt;

&lt;p&gt;module benchmarking {&lt;br/&gt;
    namespace &quot;urn:sdnhub:benchmarking&quot;;&lt;br/&gt;
    prefix benchmarking;&lt;/p&gt;

&lt;p&gt;    description &quot;This is a dummy model for benchmarking&quot;;&lt;/p&gt;

&lt;p&gt;    revision &quot;2016-03-09&quot; &lt;/p&gt;
{
        description &quot;initial version&quot;;
    }

&lt;p&gt;    container dummy1 {&lt;br/&gt;
        leaf data1 &lt;/p&gt;
{
            type uint32;
        }
&lt;p&gt;    }&lt;br/&gt;
}&lt;/p&gt;

&lt;p&gt;I populated the data1 with an integer at runtime. &lt;/p&gt;

&lt;p&gt;Then I generated a new model.jar with artifact version 0.2.0-SNAPSHOT and included the benchmarking.yang with revision-date &quot;2016-03-10&quot;. I placed this model.jar in the deploy folder of karaf. The OSGi system picked it up and installed this. The model-0.1.0-SNAPSHOT.jar and model-0.2.0-SNAPSHOT.jar are both Active in OSGi.&lt;/p&gt;

&lt;p&gt;After introducing the upgraded model, I noticed that the data in the old model was purged. This is unexpected. We need a way to preserve the current data in the old model so that the apps have an opportunity to port it over to the new model.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26071">CONTROLLER-1517</key>
            <summary>Upgrading model leads to existing data in old model being flushed</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <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="10003">Cannot Reproduce</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="srini.seetharaman@gmail.com">Srini Seetharaman</reporter>
                        <labels>
                    </labels>
                <created>Wed, 18 May 2016 03:56:03 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:10 +0000</updated>
                            <resolved>Mon, 7 Nov 2016 22:45:29 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="51425" author="rovarga" created="Tue, 21 Jun 2016 22:18:58 +0000"  >&lt;p&gt;I suspect this is actually the cluster datastore data pruner at work. Tom, can you confirm?&lt;/p&gt;</comment>
                            <comment id="51426" author="tpantelis" created="Wed, 22 Jun 2016 02:40:13 +0000"  >&lt;p&gt;Yes that sounds like the pruner although that only occurs on a karaf restart. On persistence recovery if it encounters a yang element that doesn&apos;t have a corresponding schema in the SchemaContext then it prunes it. You have to keep both schemas to avoid this.&lt;/p&gt;</comment>
                            <comment id="51427" author="srini.seetharaman@gmail.com" created="Mon, 7 Nov 2016 22:45:29 +0000"  >&lt;p&gt;In my analysis, I was using restconf to check if the data in the old model is available or not. That is an invalid test because restconf is not the right way to check old model. I did another test to use an app to check if the data in the old model exists, and it does. &lt;/p&gt;

&lt;p&gt;Marking this bug as invalid.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="26065">CONTROLLER-1511</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5905</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=5905]]></customfieldvalue>

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

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

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