[jira] [Comment Edited] (AIRFLOW-4414) AWSAthenaOperator does not push QueryExecutionID to XCom

["Marek Suppa (JIRA)" <ji...@apache.org>]

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

Marek Suppa edited comment on AIRFLOW-4414 at 5/13/19 9:31 PM:
---------------------------------------------------------------

I still believe this change is worth making, as having access to the QueryExecutionID of the executed Athena query is very useful in downstream tasks which can for instance use it to move the results out of the S3 path where they are normally stored.


was (Author: mrshu):
I still believe this change is worth making, as having access to the QueryExecutionID of the executed Athena query is very useful in downstream tasks which can for instance use it to move the results out of the

> 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
>
> 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)