Skip to content
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

Clarification: UpdateResult in SetResponse #109

Open
gsindigi opened this issue Sep 6, 2021 · 0 comments
Open

Clarification: UpdateResult in SetResponse #109

gsindigi opened this issue Sep 6, 2021 · 0 comments

Comments

@gsindigi
Copy link

gsindigi commented Sep 6, 2021

SetResponse contains repeated UpdateResult response = 2;; however, UpdateResult's fields timestamp and message (Error) fields are deprecated. Remaining two fields are to carry the path and Operation details, which are pretty much dependent on incoming SetRequest. These were making sense when each element was carrying the error information if there's any. Given this, should UpdateResult continue to be part of SetResponse? Or, should it also be considered to deprecate this as well? As the error reporting is part of the RPC return, this UpdateResult in response may not carry any useful information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant