ryansun96 commented on issue #1254:
URL: https://github.com/apache/curator/issues/1254#issuecomment-2741226410
> guarantee... the getValue will observe that value if update is success
However `getValue` is not / cannot be guaranteed to observe **that** value
even with a blocking `update` call, in the event that another `set` has
occurred in a different session, and the asynchronous watcher updates local
value before `getValue` is executed.
I think it's fair to say `setValue` makes a strong guarantee that after
success, any call to `getValue` will get **some** more updated value, whether
that value is set by the same session or a different one cannot be guaranteed
though.
If that's the intention, it should be documented, as in the case of
`trySetValue`:
> If the value has changed, the value is not set and this client's view of
the value is updated. i.e. if the value is not successful you can get the
updated value by calling {@link #getValue()}.
Whereas currently there's no mention of such in the doc of `setValue`:
> Change the shared value irrespective of its previous state
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
