airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fokko Driesprong (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AIRFLOW-610) Configuration parsing order doesn't work properly.
Date Mon, 16 Apr 2018 08:13:00 GMT

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

Fokko Driesprong resolved AIRFLOW-610.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

Issue resolved by pull request #3029
[https://github.com/apache/incubator-airflow/pull/3029]

> Configuration parsing order doesn't work properly.
> --------------------------------------------------
>
>                 Key: AIRFLOW-610
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-610
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Yongjun Park
>            Assignee: Yongjun Park
>            Priority: Major
>             Fix For: 2.0.0
>
>
> I'm testing Airflow using master branch, precisely 527e3ec.
> Documents says configuration is evaluated following order.
> # environment variable
> # configuration in airflow.cfg
> # command in airflow.cfg
> # default
> However, it can't recognize *_cmd* options.
> I added *sql_alchemy_conn_cmd* option. but it printed error below: 
> {code}
> Traceback (most recent call last):
>   File "/usr/local/bin/airflow", line 6, in <module>
>     exec(compile(open(__file__).read(), __file__, 'exec'))
>   File "/usr/local/airflow/airflow/bin/airflow", line 17, in <module>
>     from airflow import configuration
>   File "/home/airflow/airflow/__init__.py", line 30, in <module>
>     from airflow import configuration as conf
>   File "/home/airflow/airflow/configuration.py", line 733, in <module>
>     conf.read(AIRFLOW_CONFIG)
>   File "/home/airflow/airflow/configuration.py", line 585, in read
>     self._validate()
>   File "/home/airflow/airflow/configuration.py", line 497, in _validate
>     self.get('core', 'executor')))
> {code}
> I think it is affected by DEFAULT configuration. It should be changed evaluation order
as document's saying.



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

Mime
View raw message