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

Posted to commits@airflow.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2017/10/24 17:16:01 UTC

[jira] [Updated] (AIRFLOW-1732) Improve Dataflow Hook Logging

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

Chris Riccomini updated AIRFLOW-1732:
-------------------------------------
    Fix Version/s: 1.10.0

> Improve Dataflow Hook Logging
> -----------------------------
>
>                 Key: AIRFLOW-1732
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-1732
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Trevor Edwards
>            Assignee: Trevor Edwards
>             Fix For: 1.10.0
>
>
> Logging output for Dataflow hook could be a bit more useful. Namely:
> # Log the command that is used for opening a dataflow subprocess
> # If the dataflow subprocess experiences an error, log that error at warning (instead of debug)
> Currently, errors are extremely opaque, only showing the exit code. The command used is unknown and the error is logged, but it is at the debug level which makes it difficult to find.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)