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-1774 controller <p>Assume you modify an object in a DS. You need to specify the key even though you do not mean to modify it (it's immutable anyway) but you would not expect to see a WRITE notification for the leaf node that is also the key. And yet it comes. This behavior did not exist in the old "non-tree" infrastructure.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1774

Data Tree: For merge operation updates sent for keys

Bug Resolved Won't Do Josh Hershberg Josh Hershberg Tue, 19 Sep 2017 07:31:19 +0000 Tue, 25 Jul 2023 08:24:46 +0000 Tue, 22 Jan 2019 17:47:31 +0000 mdsal 0 1 <p>NB: It would appear that this is not specific to the key but in general the new infra does not check whether or not something actally changed and considers anything in the merged object as a write. I think this can be handled differently for keys which you have no choice but to specify. Perhaps there is room to differentiate between setKey and setWhateverTheNameOfTheFieldIs where if you call setKey it's not considered to be a write. Anyway, it's supposed to be immutable, no?</p> <p>I'm not following exactly what this Jira item is about. Can you provide detailed example (s)?</p> <p>Re: "This behavior did not exist in the old "non-tree" infrastructure" and "the new infra" - what are you referring to? AD-SAL, ie pre-MD-SAL?</p> <p>Josh - can you clarify this Jira further and determine if there's anything actionable needed? </p> Development External issue ID 9179 External issue URL Rank 0|i02snb: