Unnecessary subscriptions triggered when writing in operational datastore about sysrepo HOT 6 CLOSED

The problem is, when you have a hierarchical model as we do here, every subscription is woken up for any change (configuration or state) because all the modules augment the same base module... It becomes unusable very quickly.

from sysrepo.

Yes, this is expected and you had not even needed to provide an example. All the changes of a module are always communicated using a single SHM. So, when an event is generated, all the subscribers are notified because the XPath filtering is performed on the side of the subscribers.

This is a feature and works as intended. However, you are not the first to mind it so I will try to optimize it later, once I finish fixing other current issues.

from sysrepo.

OK, thanks!

from sysrepo.

So I have looked at this more and I am not sure anymore there is anything that could be optimized. The subscribers perform the filtering also because the have a filtered_out counter that can be retrieved and is needed for some statistics. Not generating an event would cause this counters to be inaccurate.

from sysrepo.

Fine, try using the new option SR_SUBSCR_FILTER_ORIG that should do what you need.

from sysrepo.

Works for me! Thanks a lot.

from sysrepo.