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

Unable to pass protobuf predefined types as repeated values and values in messages #2740

Closed
BuddhiWathsala opened this issue Feb 28, 2022 · 2 comments · Fixed by ballerina-platform/module-ballerina-grpc#733
Assignees
Labels
module/grpc Points/2.5 Priority/Low Reason/Complex Issue occurred due to complex scenario. Team/PCM Protocol connector packages related issues Type/Bug

Comments

@BuddhiWathsala
Copy link
Contributor

Description:
Currently, we can pass Any type messages, but Ballerina gRPC is unable to pass Any type arrays (i.e. repeated Any types).

Try to run a sample using the following proto definition.

syntax = "proto3";

import "google/protobuf/any.proto";

service AnyTypeArray {
  rpc unaryCall1(AnyTypeArrayRequest) returns (AnyTypeArrayResponse) {}
}

message AnyTypeArrayRequest {
    string name = 1;
    repeated google.protobuf.Any details = 2;
};

message AnyTypeArrayResponse {
   string name = 1;
   int32 code = 2;
   repeated google.protobuf.Any details = 3;
};

Related Issues

@BuddhiWathsala BuddhiWathsala self-assigned this Feb 28, 2022
@BuddhiWathsala BuddhiWathsala changed the title Unable to pass protobuf Any type arrays in Ballerina gRPC Unable to pass protobuf predefined types as repeated values and values in messages Mar 8, 2022
@BuddhiWathsala
Copy link
Contributor Author

This is applicable for other predefined types - Timestamp, Duration, and Struct

@github-actions
Copy link

This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.

      - Reason/EngineeringMistake - The issue occurred due to a mistake made in the past.
      - Reason/Regression - The issue has introduced a regression.
      - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components.
      - Reason/Complex - Issue occurred due to complex scenario.
      - Reason/Invalid - Issue is invalid.
      - Reason/Other - None of the above cases.

@BuddhiWathsala BuddhiWathsala added the Reason/Complex Issue occurred due to complex scenario. label Mar 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/grpc Points/2.5 Priority/Low Reason/Complex Issue occurred due to complex scenario. Team/PCM Protocol connector packages related issues Type/Bug
Projects
None yet
1 participant