[
https://issues.apache.org/jira/browse/AIRFLOW-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022324#comment-17022324
]
ASF subversion and git services commented on AIRFLOW-6434:
----------------------------------------------------------
Commit d580172e78e294faf214645fe9efd07a0ae5a054 in airflow's branch
refs/heads/v1-10-test from Brian Phillips
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=d580172 ]
[AIRFLOW-6434] add return statement back to DockerOperator.execute (#7013)
(cherry picked from commit a5030f31b98af24805252f6c47611290aee9c69d)
> Docker Operator No Longer XComs Result in 1.10.7
> ------------------------------------------------
>
> Key: AIRFLOW-6434
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6434
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators, xcom
> Affects Versions: 1.10.7
> Reporter: Brian Phillips
> Priority: Trivial
> Fix For: 1.10.8
>
>
> This change
> ([https://github.com/apache/airflow/commit/8a6dc6657d2a32ac3979e6478512d518ad5a5212)|https://github.com/apache/airflow/commit/8a6dc6657d2a32ac3979e6478512d518ad5a5212]
> introduced a slight (and I believe unintended) change to the Docker Operator
> xcom behavior.
> Even if xcom_push is True, DockerOperator.execute will not return a value and
> thus will not push an xcom value.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
