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/NETCONF-862 netconf <p>There is a need for an extension which has similar behavior to odl-leaf-nodes-only.<br/> The nodes which have the same data written into them are not contained in the final notification. For that we perform additional check which is costing us CPU cycles hence we do not modify the original behavior rather we are making this new extension.</p> NETCONF-862

Add changed-leaf-nodes-only subscription extension

New Feature Medium Resolved Done Peter Puškár Peter Puškár Thu, 24 Feb 2022 12:11:33 +0000 Wed, 26 Jul 2023 00:16:33 +0000 Mon, 2 Jan 2023 18:04:14 +0000 5.0.0 restconf-nb 0 2 <p>This change will change the semantics of the extension. Performing leaf-level comparison, which incurs significant CPU penalty vs. the current spec.<br/> As such, I believe this needs to be done as a separate extension with the semantics specified.</p> <p>Okay, I can make this separate extension.</p> <p>One more question though, the problem for this lies in the upstream implementation as the DataTreeCandidateNode that is passed down to serializeLeafNodesOnly is NormalizedNodeDataTreeCandidateNode (can it be other implementation?) which always returns ModificationType.WRITE in its getModificationType() implementation, even for the NormalizedNode which has same Before and After data.</p> <p>Should the semantics in the upstream implementation stay as it is and we adjust to that as downstream user here? </p> Relates NETCONF-1100 Development Rank 0|i041nb: