[
https://issues.apache.org/jira/browse/BEAM-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17546890#comment-17546890
]
Kenneth Knowles commented on BEAM-3365:
---------------------------------------
This issue has been migrated to https://github.com/apache/beam/issues/18702
> The Java SDK Harness and runners-core-construction payloads should be
> consistent
> --------------------------------------------------------------------------------
>
> Key: BEAM-3365
> URL: https://issues.apache.org/jira/browse/BEAM-3365
> Project: Beam
> Issue Type: Bug
> Components: runner-core, sdk-java-harness
> Reporter: Thomas Groh
> Priority: P3
> Labels: Clarified
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
