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

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

Commit 57a5bdbc704178fab3e63ea92c10ab13d0f56692 in airflow's branch 
refs/heads/v1-10-test from Marek Ć uppa
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=57a5bdb ]

[AIRFLOW-4414] AWSAthenaOperator: Push QueryExecutionID to XCom (#5276)

Currently it is not possible to make use of QueryExecutionID (the
unique identifier of the query submitted to Athena) in the tasks that
follow.

(cherry picked from commit 90f08aaa0065f4f1a8cb01a1a491bf3705dd0f07)


> AWSAthenaOperator does not push QueryExecutionID to XCom
> --------------------------------------------------------
>
>                 Key: AIRFLOW-4414
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-4414
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: aws
>            Reporter: Marek Suppa
>            Assignee: Marek Suppa
>            Priority: Minor
>             Fix For: 1.10.4
>
>
> AWSAthenaOperator should make it easy to push QueryExecutionID to XCom which 
> it currently does not. The best way of achieving that would currently most 
> probably be
> {code}
> class MyAWSAthenaOperator(AWSAthenaOperator):
>     def execute(self, context):
>         super(MyAWSAthenaOperator, self).execute(context)
>         # just so that this gets `xcom_push`(ed)
>         return self.query_execution_id
> {code}
> The fix should be as simple as adding {code}return 
> self.query_execution_id{code} at the end of {{execute}} function.
> I will add that as part of this task.



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

Reply via email to