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

Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 20:14:51 UTC

[GitHub] [beam] kennknowles opened a new issue, #18702: The Java SDK Harness and runners-core-construction payloads should be consistent

kennknowles opened a new issue, #18702:
URL: https://github.com/apache/beam/issues/18702

   Right now the Java SDK harness expects DoFnInfo instances within the payload of all DoFns it is provided, while the pipeline translation/ParDoTranslation/etc assumes that the ParDoTranslation channel will be used to extract useful values from the serialized form (potentially by converting to a ParDoLike). As such, a Java ParDo serialized with the Java ParDoTranslation class cannot be provided in that form to the Java SDK harness. Instead, that node has to be rewritten to include a `DoFnInfo` in the payload.
   
   This seems unreasonable, and the two should be brought in line to use the same serialized representation.
   
   Imported from Jira [BEAM-3365](https://issues.apache.org/jira/browse/BEAM-3365). Original Jira may contain additional context.
   Reported by: tgroh.


-- 
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.apache.org

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