TheNeuralBit commented on a change in pull request #16558:
URL: https://github.com/apache/beam/pull/16558#discussion_r788068515
##########
File path: model/pipeline/src/main/proto/schema.proto
##########
@@ -31,6 +31,11 @@ option go_package =
"github.com/apache/beam/sdks/v2/go/pkg/beam/model/pipeline_v
option java_package = "org.apache.beam.model.pipeline.v1";
option java_outer_classname = "SchemaApi";
+message SchemaCoderPayload {
+ Schema schema = 1;
+ map<string, bytes> sdk_information = 2;
Review comment:
I was thinking about this some more - will we ever actually get in a
situation where multiple SDKs can attach information to a schema coder? How
will that happen?
It seems like in practice just the producing SDK will attach sdk_information.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
