Automatic version management on key updates

[VishalGujela]

I’m currently using this library for Redis operations and wanted to confirm whether it supports any mechanism for automatic version updates when a key’s data is modified.

For example, given a key like:
sr:running:sr:abc-function:data:/abc-Function:abc-Function/abcFunction-Single

I’d like Redis (or the client library) to automatically maintain and increment a version (or change counter) whenever the key’s value changes — without requiring me to manually update a separate version key each time.

Specifically, I’m looking to understand:

1. Does the library natively support version tracking or automatic version incrementing on write operations?

2. If not, is there a recommended approach or extension mechanism (e.g., hooks, middleware, or Lua scripting) to achieve this?

Any guidance or best practices would be appreciated.

Thanks & regards,
Vishall

[michalvasko]

There is support only for a version of the whole datastore data of a module. If you want to track specific nodes this way, you will have to implement it yourself. Depending on the datastore backend, maybe redis or MongoDB support it natively but I do not know. And it is up to you how you want to implement this, my first idea would be to subscribe to the changes of the particular data and just update the version in the callback.

[VishalGujela]

When you say callback does it mean in the rpc response ?
Because from where i can see that in this procedure client applies the configuration and netopeer2 server manages it.
Need a little bit of clarity on this callback procedure.
Can you please help me out a bit?

[michalvasko]

As an example, you can simply subscribe using sr_module_change_subscribe() to /module:container/leaf. Then, in the callback you can simply do leaf_version++ and you have a trivial way of implementing versioning of the leaf value.