You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@beam.apache.org by "Kenneth Knowles (JIRA)" <ji...@apache.org> on 2019/03/19 03:43:00 UTC

[jira] [Commented] (BEAM-2947) SDK harnesses should be able to indicate panic in FnAPI

    [ https://issues.apache.org/jira/browse/BEAM-2947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795631#comment-16795631 ] 

Kenneth Knowles commented on BEAM-2947:
---------------------------------------

[~lcwik] [~thw] [~lostluck] is this solved?

> SDK harnesses should be able to indicate panic in FnAPI
> -------------------------------------------------------
>
>                 Key: BEAM-2947
>                 URL: https://issues.apache.org/jira/browse/BEAM-2947
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>            Reporter: Henning Rohde
>            Priority: Minor
>              Labels: portability, triaged
>
> If the SDK harness encounters a permanent problem (local file corruption or bad staged files, say) it should be able to rely that information to the runner as a "panic" message, say. Such conditions may also happen during the boot stage.
> Using process/container exit codes would likely not work well, because that information may not flow easily to the runner logic depending on how containers are managed.



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