You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Ismaël Mejía (JIRA)" <ji...@apache.org> on 2019/04/19 09:00:00 UTC

[jira] [Updated] (BEAM-3072) Improve error handling at staging time for DataflowRunner

     [ https://issues.apache.org/jira/browse/BEAM-3072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía updated BEAM-3072:
-------------------------------
    Summary: Improve error handling at staging time for DataflowRunner  (was: Improve error handling at staging time time for DataflowRunner)

> Improve error handling at staging time for DataflowRunner
> ---------------------------------------------------------
>
>                 Key: BEAM-3072
>                 URL: https://issues.apache.org/jira/browse/BEAM-3072
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-py-core
>            Reporter: Ahmet Altay
>            Assignee: niklas Hansson
>            Priority: Minor
>              Labels: starter, triaged
>             Fix For: 2.12.0
>
>          Time Spent: 7h
>  Remaining Estimate: 0h
>
> dependency.py calls out to external process to collect dependencies:
> https://github.com/apache/beam/blob/de7cc05cc67d1aa6331cddc17c2e02ed0efbe37d/sdks/python/apache_beam/runners/dataflow/internal/dependency.py#L263
> If these calls fails, the error is not clear. The error only tells what failed but does not show the actual error message, and is not helpful for users.
> As a general fix processes.py should have general better output collection from failed processes.



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