airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-319) Optionally push HTTP response from HTTP_simple_operator to XCom
Date Sun, 23 Oct 2016 13:21:58 GMT

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

ASF subversion and git services commented on AIRFLOW-319:
---------------------------------------------------------

Commit 3e3ccb7c68d3eeef3d75448731b8565ab99f2fe2 in incubator-airflow's branch refs/heads/master
from [~jzelenkov]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=3e3ccb7 ]

[AIRFLOW-319]AIRFLOW-319] xcom push response in HTTP Operator

Adds optional parameter to push response of the
HTTP Operator to XCom

Documentation suggests that any operator's execute
method that returns
value should push it into XCom:
http://airflow.incubator.apache.org/concepts.html#
xcoms

> In addition, if a task returns a value (either
from its Operator’s
execute() method, or from a PythonOperator’s
python_callable
function), then an XCom containing that value is
automatically pushed.

Closes #1658 from jzelenkov/AIRFLOW-
319_xcom_push_http_response


> Optionally push HTTP response from HTTP_simple_operator to XCom
> ---------------------------------------------------------------
>
>                 Key: AIRFLOW-319
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-319
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: operators
>    Affects Versions: Airflow 1.7.1.3
>            Reporter: Jay Zelenkov
>            Assignee: Jay Zelenkov
>            Priority: Minor
>             Fix For: Airflow 1.8
>
>
> Documentation suggests that any operator's execute method that returns value should push
it into XCom: http://airflow.incubator.apache.org/concepts.html#xcoms
> {quote}
> In addition, if a task returns a value (either from its Operator’s execute() method,
or from a PythonOperator’s python_callable function), then an XCom containing that value
is automatically pushed.
> {quote}
> ----
> This issue addresses missing xcom push behavior in {{http_operator}}
> Current implementation follows a pattern used in {{BashOperator}} and suggested by [mistercrunch|https://github.com/mistercrunch]
in [GitHub PR 658|https://github.com/apache/incubator-airflow/pull/658]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message