You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2019/04/23 12:38:00 UTC
[jira] [Updated] (AIRFLOW-3951) No easy way to get
query_execution_id from AWSAthenaOperator
[ https://issues.apache.org/jira/browse/AIRFLOW-3951?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor updated AIRFLOW-3951:
---------------------------------------
Summary: No easy way to get query_execution_id from AWSAthenaOperator (was: No easy way to get query_execution_id from AWSAthensOperator)
> No easy way to get query_execution_id from AWSAthenaOperator
> -------------------------------------------------------------
>
> Key: AIRFLOW-3951
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3951
> Project: Apache Airflow
> Issue Type: Improvement
> Components: aws, contrib, operators
> Affects Versions: 1.10.2
> Reporter: Rob Dinoff
> Priority: Major
>
> There does not seem to be an easy way to get the query_execution_id from the AWSAthensOperator. This should be pushed as an xcom variable. Need this so query_execution_id can be used in the AthenaSensor.
> The following should be added to the end of the AWSAthenaOperator.execute
> {code:java}
> context["task_instance"].xcom_push(key="query_execution_id", value=self.query_execution_id){code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)