[
https://issues.apache.org/jira/browse/BEAM-10110?focusedWorklogId=438876&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-438876
]
ASF GitHub Bot logged work on BEAM-10110:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/May/20 17:54
Start Date: 29/May/20 17:54
Worklog Time Spent: 10m
Work Description: lostluck commented on pull request #11832:
URL: https://github.com/apache/beam/pull/11832#issuecomment-636104610
Yup, runner v2 solved that issue. Merging.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 438876)
Time Spent: 1h (was: 50m)
> Populate pipeline_proto_coder_id field for dataflow.
> ----------------------------------------------------
>
> Key: BEAM-10110
> URL: https://issues.apache.org/jira/browse/BEAM-10110
> Project: Beam
> Issue Type: Task
> Components: runner-dataflow, sdk-go
> Reporter: Robert Burke
> Assignee: Robert Burke
> Priority: P2
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Dataflow isn't natively translating from the Beam Pipeline Proto yet, but
> requires SDKs to translate the graph into it's own format. Adding this hint
> for custom coders (Coders not known to Dataflow/Beam) avoids having dataflow
> re-synthesize coders from it's format, back to the pipeline proto.
> Currently there's the awkward restriction on which coders should receive the
> ID, rather than having the SDK apply the field to all of them, but this is a
> good first step to get there. This restriction may be lifted on a subsequent
> dataflow release.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
