You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2018/09/02 18:01:03 UTC

[jira] [Commented] (AIRFLOW-2586) Stop getting AIRFLOW_HOME value from config file in bash operator

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

Apache Spark commented on AIRFLOW-2586:
---------------------------------------

User 'yrqls21' has created a pull request for this issue:
https://github.com/apache/incubator-airflow/pull/3484

> Stop getting AIRFLOW_HOME value from config file in bash operator
> -----------------------------------------------------------------
>
>                 Key: AIRFLOW-2586
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2586
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Kevin Yang
>            Assignee: Kevin Yang
>            Priority: Major
>
> Before [this commit|https://github.com/apache/incubator-airflow/commit/a0deb506c070637abc3c426bc7d060e3fe6c854d#diff-30054b6fa334216ba6e66c9f07025cd2R35] subprocess created by bash operator inherits env vars from the parent process. However, it does not inherit the proper env var from the `airflow worker` process because we had a bug in the `sudo airflow run --raw` command. The commit was created to address the bug for bash operator. The bug was later on fixed in [this commit|https://github.com/apache/incubator-airflow/commit/354492bc597130f43c76e7bec4bc894fb6deb7fe] and thus bash operator does not need and should not get AIRFLOW_HOME value from the config (otherwise there might be discrepancy between the AIRFLOW_HOME value in the parent process and the child process).



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