-
Notifications
You must be signed in to change notification settings - Fork 9.8k
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
*: allow user-provided watch ID to mvcc #9065
Conversation
@xiang90 PTAL. Added clientv3 watch response cancel field check (in addition to |
Signed-off-by: Gyuho Lee <[email protected]>
Signed-off-by: Gyuho Lee <[email protected]>
Signed-off-by: Gyuho Lee <[email protected]>
This allows for watchers to be created concurrently without needing potentially complex and latency-adding queuing on the client. Signed-off-by: Gyuho Lee <[email protected]>
Signed-off-by: Gyuho Lee <[email protected]>
Signed-off-by: Gyuho Lee <[email protected]>
Codecov Report
@@ Coverage Diff @@
## master #9065 +/- ##
=========================================
Coverage ? 76.08%
=========================================
Files ? 359
Lines ? 29959
Branches ? 0
=========================================
Hits ? 22794
Misses ? 5588
Partials ? 1577
Continue to review full report at Codecov.
|
Signed-off-by: Gyuho Lee <[email protected]>
lgtm |
@gyuho you might want to check with @fanminshi to make sure jetcd is not affected. |
Smaller changes in server-side from #9015.
Plus, clientv3 change to handle non
-1
watch ID (butCanceled==true
).Watch ID is only configurable to mvcc/v3rpc for the use of other language client bindings.
Go
clientv3
will still auto-generate watch IDs.Cherry-pick #8662.
Fix #7036.