[
https://issues.apache.org/jira/browse/BEAM-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17250521#comment-17250521
]
Boyuan Zhang edited comment on BEAM-3245 at 12/16/20, 7:05 PM:
---------------------------------------------------------------
> How does a runner use Fn API to indicate shutdown/teardown?
There is no way unless we change the way how tearDown is invoked in sdk harness
or we introduce such a way.
Do we have a case that we don't kill the process instead we wait for it to
terminate? If in the portable execution the tearDown is never called, should we
mark the API as deprecated?
was (Author: boyuanz):
> How does a runner use Fn API to indicate shutdown/teardown?
There is no way unless we change the way how tearDown is invoked in sdk harness.
Do we have a case that we don't kill the process instead we wait for it to
terminate?
> Dataflow runner does not respect ParDo's lifecycle on case of exceptions
> ------------------------------------------------------------------------
>
> Key: BEAM-3245
> URL: https://issues.apache.org/jira/browse/BEAM-3245
> Project: Beam
> Issue Type: Bug
> Components: runner-dataflow
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Ismaël Mejía
> Priority: P3
>
> The lifecycle of the DoFn is not respected in case of exception in any of the
> lifecycle methods after setup.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
