[MDSAL-211] Initial DCN on pre-existing data when registering on a list node is partial Created: 30/Nov/16  Updated: 09/Mar/18  Resolved: 15/Dec/16

Status: Resolved
Project: mdsal
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Guy Sela Assignee: Tom Pantelis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 7271

 Description   

When registering a DataBroker Listener on a certain path, the initial data event should contain all pre-existing data.
In the case of a List node, the initial data event only contains one element instead of all elements.
For example:
"
container elan-instances {
list elan-instance {
...
"
When registering a listener on the path:
InstanceIdentifier.create(ElanInterfaces.class).child(ElanInterface.class))

the initial will only contain a single ElanInterface even though there are multiple ElanInterface's in the MD-SAL.



 Comments   
Comment by Tom Pantelis [ 01/Dec/16 ]

Submitted https://git.opendaylight.org/gerrit/#/c/48846/ to modify AbstractDOMStoreTreeChangePublisher in mdsal. Will submit another patch in controller to convert DefaultShardDataTreeChangeListenerPublisher to use it.

Comment by Tom Pantelis [ 13/Dec/16 ]

Controller patch https://git.opendaylight.org/gerrit/#/c/48903/

Generated at Wed Feb 07 20:09:03 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.