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 2017/12/02 11:39:00 UTC
[jira] [Created] (AIRFLOW-1880) TaskInstance.log_filepath property
doesn't account for custom format
Ash Berlin-Taylor created AIRFLOW-1880:
------------------------------------------
Summary: TaskInstance.log_filepath property doesn't account for custom format
Key: AIRFLOW-1880
URL: https://issues.apache.org/jira/browse/AIRFLOW-1880
Project: Apache Airflow
Issue Type: Bug
Affects Versions: 1.9.0
Reporter: Ash Berlin-Taylor
Priority: Trivial
Fix For: 1.9.1
The "log_filepath" property on a TaskInstance doesn't output the right path after [AIRFLOW-1582] which changed the default and let the format be customized.
This is a minor bug that doesn't affect very much - it's displayed in the admin UI, and is included in the failure email. Beyond that it isn't used anywhere by Airflow.
Also I wonder if the log_filepath should be an attribute of the Job model, so that if the format is changed in the future we can still find the right historic log file?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)