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-1099 netconf <p>RESTCONF northbound's data service contains a special case on access to ietf-restconf-monitoring's stream state: on each access we write populate streams derived from individual notifications. This was introduced for unknown reasons in <a href="https://jira.opendaylight.org/browse/NETCONF-342" title="Make notifications defined by yangs automatic loaded for streaming" class="issue-link" data-issue-key="NETCONF-342"><del>NETCONF-342</del></a>, which also removed implementation for sal-remote.yang's create-notification-stream.</p> <p>Effectively revert <a href="https://jira.opendaylight.org/browse/NETCONF-342" title="Make notifications defined by yangs automatic loaded for streaming" class="issue-link" data-issue-key="NETCONF-342"><del>NETCONF-342</del></a>, as it just does not make sense, restoring proper support creating notification streams.</p> NETCONF-1099

Restore sal-remote create-notification-stream functionality

Improvement High Resolved Done Robert Varga Robert Varga pt Tue, 25 Jul 2023 18:03:32 +0000 Mon, 30 Oct 2023 13:03:40 +0000 Mon, 30 Oct 2023 13:03:40 +0000 7.0.0 restconf-nb 0 1 <p>As part of this change we need to also rehost notification stream naming to ListenersBroker and then refactor them so the stream names do not carry all the metadata about how to establish them.</p> Blocks NETCONF-1102 Relates NETCONF-342 Development Rank 0|i045xj: