You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
Is the "updates_only" field in the SubscribeRequest message meant for sending "delta" only instead of "absolute" values of the current state, or is it about the initial synchronization during the Subscription not to send the current state at that time, and just keep sending updates in the state after that as per the subscription type?
Thanks..
The text was updated successfully, but these errors were encountered:
The "updates_only" does not change the values that are delivered for the
updates. Counters would still be absolute. This mechanism is used to skip
the synchronization phase and is useful in the context of event-driven
telemetry where a client might only be interested in receiving updates when
changes occur.
A couple example use cases:
- Subscribe to the configuration paths with "updates_only", push a
configuration, record the delay with which changes are reflected back over
telemetry
- Subscribe to RIB with "updates_only", track how much churn is occurring
On Thu, Dec 14, 2017 at 6:31 PM, Mohamed ***@***.***> wrote:
Hi,
Is the "updates_only" field in the SubscribeRequest message meant for
sending "delta" only instead of "absolute" values of the current state, or
is it about the initial synchronization during the Subscription not to send
the current state at that time, and just keep sending updates in the state
after that as per the subscription type?
Thanks..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#82>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ARfILx98ZCfMI5YlGz-gvz6D6HBYWE-6ks5tAdoNgaJpZM4RC769>
.
Hi,
Is the "updates_only" field in the SubscribeRequest message meant for sending "delta" only instead of "absolute" values of the current state, or is it about the initial synchronization during the Subscription not to send the current state at that time, and just keep sending updates in the state after that as per the subscription type?
Thanks..
The text was updated successfully, but these errors were encountered: