[
https://issues.apache.org/jira/browse/BEAM-8672?focusedWorklogId=344667&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-344667
]
ASF GitHub Bot logged work on BEAM-8672:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Nov/19 23:42
Start Date: 15/Nov/19 23:42
Worklog Time Spent: 10m
Work Description: robertwb commented on issue #10128: [BEAM-8672] Keep
Python process alive when using LOOPBACK execution mode
URL: https://github.com/apache/beam/pull/10128#issuecomment-554570991
Is the user not doing `wait_until_finish` manually? (Or preferably, using
the `with beam.Pipeline() as p: ...` syntax?
I agree that if we make this blocking, it should be in the portable runner
code, not the flink runner.
----------------------------------------------------------------
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: 344667)
Time Spent: 0.5h (was: 20m)
> Loopback execution mode will exit before execution can begin
> ------------------------------------------------------------
>
> Key: BEAM-8672
> URL: https://issues.apache.org/jira/browse/BEAM-8672
> Project: Beam
> Issue Type: Bug
> Components: runner-flink, sdk-py-core
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> A user reported that the default LOOPBACK execution with the Python
> {{flink_runner}} does not do anything. The reason was that we need to block
> after running the pipeline in order for the embedded Python SDK Harness to
> stay alive.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
