Explicit reading of list keys using subtree filtering 51/93351/12
authorJaroslav Tóth <jtoth@frinx.io>
Sun, 25 Oct 2020 07:43:08 +0000 (08:43 +0100)
committerRobert Varga <nite@hq.sk>
Sun, 21 Feb 2021 17:19:19 +0000 (17:19 +0000)
commit91a9f1b584e1f5d6dd3c30d3d23773ab71acb46b
tree03437630e554a8dc7e7272e0a52bfe756c6c144f
parent4ba390a033e1ac39c5b75cd24c6f9d415ea7fda3
Explicit reading of list keys using subtree filtering

- According to RFC-6241, section 6.2.5, NETCONF server doesn't
  have to provide values of list keys, if NETCONF client doesn't
  ask for these fields; see following statement:

  o  If any sibling nodes of the selection node are instance
     identifier components for a conceptual data structure (e.g.,
     list key leaf), then they MAY also be included
     in the filter output.

JIRA: NETCONF-735
Change-Id: I9bb048010578fd89190f616664e2175c3d3326ae
Signed-off-by: Jaroslav Tóth <jtoth@frinx.io>
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>
netconf/netconf-util/src/main/java/org/opendaylight/netconf/util/StreamingContext.java
netconf/sal-netconf-connector/src/test/java/org/opendaylight/netconf/sal/connect/netconf/schema/mapping/NetconfMessageTransformerTest.java