Michal Vasko

Hi, unfortunately, *sysrepo* does not support annotations. Regards, Michal

I do not fully understand what you are proposing but I am quite sure it now works correctly and optimizations without measurements backing them are generally useless and make no...

What makes you think `-u` was removed? Regarding `-C`, it was removed because it is no longer needed, you can change the YANG context whether there are any connections or...

You mean that, for example, you have some subscribed `running` data that are copied into `operational` and you want to replace these with some other data? You cannot because these...

In short, the way it worked before was causing the internals to be too complex and inefficient, maintaining these operational data, so I have decided to simplify them at the...

You will have to use `sr_oper_delete_item_str()`, then `sr_edit_batch()` and then `sr_apply_changes()`.

Right, there is no lock but it will not work this way, I have only partly corrected what you wrote. I meant `sr_oper_delete_item_str()` with `sr_apply_changes()` and then `sr_edit_batch()` with `sr_apply_changes()`....

Just note that the `operational` datastore is a tricky one and the stored oper data are among the most complex features of *sysrepo*. Even when implementing it I was hoping...

Yes, there is. A single SHM segment is used to communicate all changes in a YANG module. But there could be lots of subscribers to changes of this particular YANG...

What would you suggest this option does? There is a single SHM segment meaning the best I could do is filter only the data for each subscription and then write...