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

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

                Author: ASF GitHub Bot
            Created on: 11/May/18 22:15
            Start Date: 11/May/18 22:15
    Worklog Time Spent: 10m 
      Work Description: jkff commented on issue #5285: [BEAM-2597] Flink batch 
ExecutableStage operator
URL: https://github.com/apache/beam/pull/5285#issuecomment-388499082
 
 
   Yeah your PR doesn't change any code that could possibly affect this test - 
the entire PR is in runners/flink, except for a new class and a change in 
comments. The test also has passed in the current pending run according to the 
gradle output. I'm gonna just merge it.

----------------------------------------------------------------
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: 101322)
    Time Spent: 4h  (was: 3h 50m)

> FlinkRunner ExecutableStage batch operator
> ------------------------------------------
>
>                 Key: BEAM-2597
>                 URL: https://issues.apache.org/jira/browse/BEAM-2597
>             Project: Beam
>          Issue Type: Sub-task
>          Components: runner-flink
>            Reporter: Kenneth Knowles
>            Assignee: Ben Sidhom
>            Priority: Major
>              Labels: portability
>          Time Spent: 4h
>  Remaining Estimate: 0h
>
> This operator will execute user code in the context of an SDK harness by 
> constructing a ProcessBundleDescriptor from an ExecutableStage (physical 
> stage plan) and sending instructions/elements over the control and data 
> planes.



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

Reply via email to