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

Michael Ghen closed AIRFLOW-3261.
---------------------------------
    Resolution: Works for Me

Nvm, saw this is in the logs but at the very end

> Add All BigQuery Job Errors to Logs
> -----------------------------------
>
>                 Key: AIRFLOW-3261
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3261
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Michael Ghen
>            Assignee: Michael Ghen
>            Priority: Minor
>
> When running a BigQuery load job, errors reported only contain the final 
> error. This hides information about the real error. The only workaround is to 
> log into the GCP console and find the logs in Logging using the job's ID.
> The `error_result` is selected for the Exception. All errors are stored in 
> `errors` in the job's status.
> [https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/hooks/bigquery_hook.py#L1080]
> In the google-cloud-python package, you can see they implement methods for 
> `error_result` and `errors` 
> ([https://github.com/googleapis/google-cloud-python/blob/333c52a6c4d825d8c739833e24ef7d021bb5d1c4/bigquery/google/cloud/bigquery/job.py#L445)]
>  
> This enhancement would change the output to include all errors and not just 
> the final result.
>  
>  



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

Reply via email to