[ 
https://issues.apache.org/jira/browse/BEAM-6067?focusedWorklogId=166153&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-166153
 ]

ASF GitHub Bot logged work on BEAM-6067:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Nov/18 22:32
            Start Date: 14/Nov/18 22:32
    Worklog Time Spent: 10m 
      Work Description: lukecwik commented on issue #7045: [BEAM-6067] Specify 
pipeline_coder_id property in non-Beam-standard CloudObject coders.
URL: https://github.com/apache/beam/pull/7045#issuecomment-438843877
 
 
   Run Dataflow ValidatesRunner

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 166153)
            Time Spent: 0.5h  (was: 20m)
    Remaining Estimate: 167.5h  (was: 167h 40m)

> Dataflow runner should include portable pipeline coder id in CloudObject 
> coder representation
> ---------------------------------------------------------------------------------------------
>
>                 Key: BEAM-6067
>                 URL: https://issues.apache.org/jira/browse/BEAM-6067
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Craig Chambers
>            Assignee: Kenneth Knowles
>            Priority: Major
>   Original Estimate: 168h
>          Time Spent: 0.5h
>  Remaining Estimate: 167.5h
>
> When translating a BeamJava Coder into the DataflowRunner's CloudObject 
> property map, include a property that specifies the id in the Beam model 
> Pipeline coders map corresponding to that Coder.  This will allow the 
> DataflowRunner to reference the corresponding Beam coder in the FnAPI 
> processing bundle.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to