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

Posted to commits@airflow.apache.org by "Sergio Kef (Jira)" <ji...@apache.org> on 2019/11/19 20:52:00 UTC

[jira] [Created] (AIRFLOW-6016) Remove redundant config option `remote_logging`

Sergio Kef created AIRFLOW-6016:
-----------------------------------

             Summary: Remove redundant config option `remote_logging`
                 Key: AIRFLOW-6016
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6016
             Project: Apache Airflow
          Issue Type: Improvement
          Components: logging
    Affects Versions: 1.10.6
            Reporter: Sergio Kef
            Assignee: Sergio Kef


Configuration ({{airflow.cfg}}) sets the boolean value {{remote_logging}} along with the {{remote_base_log}} as well as some others, in order to configure remote logging destinations (s3, gcs, etc).

My understanding is that the {{remote_logging}} variable is useless, it only works as a master to enable situations where remote_base_log is set but the actual remote logging is disabled.

I find this a bad design decision, as I (as a user) don't understand the reason of its existence and the significance of changing it.



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