[
https://issues.apache.org/jira/browse/BEAM-3365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17131800#comment-17131800
]
Beam JIRA Bot commented on BEAM-3365:
-------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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: P2
> Labels: stale-P2
>
> 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.3.4#803005)
