[
https://issues.apache.org/jira/browse/BEAM-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251338#comment-17251338
]
Kenneth Knowles commented on BEAM-3245:
---------------------------------------
The original reason for introducing {{@TearDown}} is still important. Quickly
scanning the code, it seems {{@TearDown}} is used. So I think portability needs
to reach parity.
Re-reading this ticket, it does not seem to be about killing the process. If
there is an exception in the DoFn method, the SDK harness should handle this
and call teardown.
I also think that the Fn API needs to have an instruction that can be sent to a
harness for graceful shutdown, including calling {{@TearDown}}, but that might
be a different issue.
> 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)
