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

Posted to commits@airflow.apache.org by "Kamil Bregula (Jira)" <ji...@apache.org> on 2019/11/26 23:12:00 UTC

[jira] [Commented] (AIRFLOW-6074) Logging to Azure Blob Storage

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

Kamil Bregula commented on AIRFLOW-6074:
----------------------------------------

Thanks for reporting it. 

I will try to improve it in my PR.

[https://github.com/apache/airflow/pull/6644]

> Logging to Azure Blob Storage
> -----------------------------
>
>                 Key: AIRFLOW-6074
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6074
>             Project: Apache Airflow
>          Issue Type: Bug
>          Components: logging
>    Affects Versions: 1.10.6
>            Reporter: david diaz
>            Priority: Major
>         Attachments: image-2019-11-26-13-20-13-271.png
>
>
> The template in airflow/airflow/config_templates/airflow_local_setting.py contains a hard coded name for the wasb_container attribute in REMOTE_HANDLERS
>  
> !image-2019-11-26-13-20-13-271.png!
> The azure blob hook uses that name to look for the container to place the logs, but if it fails due to that container not existing it will log that the container doesnt exist using the name of the enviromental variable REMOTE_BASE_LOG_FOLDER . Either the logging or the hardcoded value should be changed.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)