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

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/04/23 09:47:00 UTC

[jira] [Resolved] (AIRFLOW-572) Remote (S3) log gets overridden when a task is executed again

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

Ash Berlin-Taylor resolved AIRFLOW-572.
---------------------------------------
    Resolution: Fixed

Think this has been fixed for a while (~1.9 timeframe) now.

> Remote (S3) log gets overridden when a task is executed again
> -------------------------------------------------------------
>
>                 Key: AIRFLOW-572
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-572
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Michael Spector
>            Priority: Major
>
> The log filename is given a suffix of execution_date, which can be the same for all invocations of the same DAG run, for instance: "2016-10-15T00:00:00". 
> Options I see:
> * There's an option called 'append' in S3 logging mechanism, but there's no way to use it. This option could be added to the configuration file.
> * start_date could be used as a suffix instead of execution_date, this way every task invocation would have its own log file.



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