-
Notifications
You must be signed in to change notification settings - Fork 171
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 metadata in state bulk get state #114
Conversation
/cc @mchmarny |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@skyao thanks for the PR. You can update the protos in the go SDK by running make protos
so you can uncomment the BulkStateItem
bits and we land a clean PR. Also, could please expand the existing test to cover the metadata bits your PR adds to state. We have test coverage thresholds in place so adding these new fields to test will ensure the PR passes.
OK, I will try to update the protos and generated go source code. But I meet one problem: when I run "make protos" successfully without change the protos, the generated code is big different with curernt files. I think this difference due to the version of the tools. Since I don't find any review requirements in go-sdk repo, I tried to find in dapr repo and found this:
Should we use the save version in go-sdk? |
I update to use above version, the generated code is the same as commited in dapr/dapr repo. But it is big different with the one in go sdk. And in // Code generated by protoc-gen-go. DO NOT EDIT.
// versions:
// protoc-gen-go v1.25.0
// protoc v3.13.0
// source: dapr/proto/runtime/v1/dapr.proto Compare to the version requirements in dapr/dapr:
So to generated the code in go-sdk, which version should we use? |
We should follow the newer one, in dapr/dapr. Let me take a look at the setup in makefile. |
OK, so ye, we should use the new one. The // protoc-gen-go v1.25.0
// protoc v3.14.0 I know @youngbupark was going to be updating the protoc in dapr/dapr. Let me update the protos in a separate PR then you can re-base on that. |
OK, I got #116 in, one this lands you can update the metadata PR. |
OK, #116 landed, so you just need to resolve these few conflicts and you should be good to go. |
@mchmarny Code rebased now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left a couple of comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
update GetBulkState method:
The details of this PR is discussed in dapr issue :
dapr/dapr#2368
dapr/dapr#2498