You are viewing a plain text version of this content. The canonical link for it is here.

Posted to github@beam.apache.org by "mynameborat (via GitHub)" <gi...@apache.org> on 2023/04/19 14:28:37 UTC

[GitHub] [beam] mynameborat commented on pull request #26276: Populate TransformIOMap as Config for Beam Samza Runner

mynameborat commented on PR #26276:
URL: https://github.com/apache/beam/pull/26276#issuecomment-1514840227

   General questions
   1. Why use JSON as the serialization format when protobuf is the recommended way of serializing internal components within beam? 
   2. Can we leverage existing protobuf representation of the pipeline and use that instead of JSON? i.e., populating the same configuration w/ toProto(pipeline) and deserializing from the config?
   3. Are there any potential pitfalls with varying versions of jackson across beam and samza which can cause issues?
   
   


-- 
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: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org