-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for RequestProgress for Watch? #928
Comments
A PR would be very welcome ! |
Excellent, thanks @lburgazzoli! I'll take a shot at a PR, using the Go client change as a reference. |
Added a function that requests a watch stream progress status be sent in the watch response stream as soon as possible. This is helpful in situations where an application may want to check the progress of a watch to determine how up-to-date the watch stream is. Addresses etcd-io#928
Added a function that requests a watch stream progress status be sent in the watch response stream as soon as possible. This is helpful in situations where an application may want to check the progress of a watch to determine how up-to-date the watch stream is. Addresses etcd-io#928
Added a function that requests a watch stream progress status be sent in the watch response stream as soon as possible. This is helpful in situations where an application may want to check the progress of a watch to determine how up-to-date the watch stream is. Addresses etcd-io#928
PR opened for this change #957 |
Thanks @juliankung-db! (we work at same company). After this merges, @lburgazzoli do you know how soon a new release including it might be available? We're trying to weigh different options for being able to use this functionality in our company's codebase. Many thanks! |
I can release as often as it is needed so I'll have a look at the pr tomorrow then we can discuss about a release |
Added a function that requests a watch stream progress status be sent in the watch response stream as soon as possible. This is helpful in situations where an application may want to check the progress of a watch to determine how up-to-date the watch stream is. Addresses etcd-io#928
Added a function that requests a watch stream progress status be sent in the watch response stream as soon as possible. This is helpful in situations where an application may want to check the progress of a watch to determine how up-to-date the watch stream is. Addresses #928
Thanks for the quick turnaround on the review and merge @lburgazzoli :^) In terms of the release, it'd be great on our side if it'd be possible to create a new release in the next week or two (please let us know if we can help). If not, we can look at short-term workarounds until the next release. |
I can plan to do a release over the week-end or beginning next week. |
Hey I just wanted to quickly ping for an update on the release. Will the release be happening around the beginning of next week (8/9)? |
Sorry for the delay, I have released it now. |
@juliankung-db can we close this issue now ? |
Yep, looks like everything's good and working on our end, thanks :^) Feel free to close it, @mikehuston is OOO until next week so he won't be able to close it until then |
I'd like to use the RequestProgress functionality added etcd-io/etcd#9869 in this Java etcd client.
Use case is similar to the one mentioned in that PR; I'd like to maintain an in-memory cache of an etcd key range and use RequestProgress in combination with a quorum read so that I can know when my cached data may be out of date.
I looked at the Watch interface and impl and it did not appear RequestProgress support had been added yet. Are there plans to add this functionality and/or would you welcome a pull request if I can find time?
The text was updated successfully, but these errors were encountered: