You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jay Zelenkov (JIRA)" <ji...@apache.org> on 2016/07/08 15:21:10 UTC
[jira] [Updated] (AIRFLOW-319) Optionally push HTTP response from
HTTP_simple_operator to XCom
[ https://issues.apache.org/jira/browse/AIRFLOW-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jay Zelenkov updated AIRFLOW-319:
---------------------------------
Affects Version/s: (was: Airflow 1.8)
Airflow 1.7.1.3
External issue URL: https://github.com/apache/incubator-airflow/pull/1658
> 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)