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/CONTROLLER-220 controller <p>I'm trying to provide a configuration facility to my bundle, where the configuration state can be updated over the Restconf interface, and my code reacts to those changes via onDataChange events.</p> <p>I would like to raise that the current DataChange events are quite counter-intuitive to use. While practically it is possible to deduce what happened, it would be more convenient if the reported maps/sets contained only what their name suggests.</p> <p>1) When a new configuration element is created, it appears both as "created" and "updated". It would be more convenient if created elements would only be reported as "created".</p> <p>2) When a configuration element is updated with identical data (i.e., did not change), it is still reported as "updated". It would be useful if such identical updates were filtered by the data store internals, and would not be reported to the listeners.</p> <p>3) When a configuration element is deleted, it is not reported as "removed"; it only appears among the "original" elements. It would be useful if was contained among the "removed" elements as well.</p> <p>I have attached a bundle which can be used to reproduce what happens. Check the readme.txt file for details.</p> <p>Operating System: Linux<br/> Platform: PC</p> CONTROLLER-220

DataChange even is inconsistent with changes in the data store via Restconf

Bug Resolved Cannot Reproduce Tony Tkacik Zoltan Lajos Kis Thu, 20 Mar 2014 08:42:54 +0000 Tue, 25 Jul 2023 08:23:15 +0000 Mon, 19 May 2014 08:20:59 +0000 mdsal 0 3 <p>Attachment restconftest.tar.gz has been added with description: bundle to reproduce the bug</p> <p>The similar issues are seen when I try to listen the data change event on Topology changes.</p> <p>If you register listener for Links like following - </p> <p>dataService.registerDataChangeListener(<br/> InstanceIdentifier.builder(NetworkTopology.class).child(Topology.class, new TopologyKey(new TopologyId("flow:1")))<br/> .child(Link.class).toInstance(), new TopologyListener()); </p> <p>Where my TopologyListener class, which implements DataChangeListener looks like following - </p> <p>public class TopologyListener implements DataChangeListener{</p> <p> @Override<br/> public void onDataChanged(<br/> DataChangeEvent&lt;InstanceIdentifier&lt;?&gt;, DataObject&gt; change) </p> { Map&lt;InstanceIdentifier&lt;?&gt;, DataObject&gt; linkCreated = change.getCreatedOperationalData(); Set&lt;InstanceIdentifier&lt;?&gt;&gt; linkRemoved = change.getRemovedOperationalData(); } <p>Now, whenever a new link is removed, change.getRemovedOperationalData() does not have data, its empty Set. That information should be available.</p> <p>I am trying to listen to MD-SAL topology changes, specifically creation and removal of links. <br/> Other steps to reproduce (from <a href="https://jira.opendaylight.org/browse/CONTROLLER-241" title="Topology data change event does not provide link removal data" class="issue-link" data-issue-key="CONTROLLER-241"><del>CONTROLLER-241</del></a>)</p> <p>I register my listener for Links like following - </p> <p>dataService.registerDataChangeListener(<br/> InstanceIdentifier.builder(NetworkTopology.class).child(Topology.class, new TopologyKey(new TopologyId("flow:1")))<br/> .child(Link.class).toInstance(), new TopologyListener()); </p> <p>Where my TopologyListener class, which implements DataChangeListener looks like following - </p> <p>public class TopologyListener implements DataChangeListener{</p> <p> @Override<br/> public void onDataChanged(<br/> DataChangeEvent&lt;InstanceIdentifier&lt;?&gt;, DataObject&gt; change) </p> { Map&lt;InstanceIdentifier&lt;?&gt;, DataObject&gt; linkCreated = change.getCreatedOperationalData(); Set&lt;InstanceIdentifier&lt;?&gt;&gt; linkRemoved = change.getRemovedOperationalData(); } <p>Now, when a link is removed, change.getRemovedOperationalData() does not have data, its empty Set.</p> <p>Data Change Events were fixed at master over last 3 weeks.</p> <p>This behaviour should be fixed.</p> Duplicate CONTROLLER-241 Development External issue ID 554 External issue URL Priority Rank 0|i02j1z: