[GitHub] [airflow] Taragolis commented on issue #34583: Support split_statements AthenaOperator [Amazon provider]

["Taragolis (via GitHub)" <gi...@apache.org>]

Taragolis commented on issue #34583:
URL: https://github.com/apache/airflow/issues/34583#issuecomment-1733199882

   > The existing AthenaOperator only waits async/sync for the query to complete; it doesn't retrieve or process the results.
   
   `AthenaHook` is wrapper around `boto3`, which are not DBApi2 complaint, so if required reuse `SQLExecuteQueryOperator` then basically need to create separate hook. By the same way as it implemented for Redshift:
   - [`RedshiftDataHook`](https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/_modules/airflow/providers/amazon/aws/hooks/redshift_data.html#RedshiftDataHook) wrapper around `boto3`
   - [`RedshiftSQLHook`](https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/_modules/airflow/providers/amazon/aws/hooks/redshift_sql.html#RedshiftSQLHook) wrapper around [`redshift_connector`](https://github.com/aws/amazon-redshift-python-driver) and [`sqlalchemy_redshift`](https://github.com/sqlalchemy-redshift/sqlalchemy-redshift)
   
   > SQLExecuteQueryOperator does not provide a trigger for async wait of query executions.
   
   Most of the drivers which are used are sync, and many of dialects have only provided sync implementation
   
   > To address these cases, I propose two potential implementations
   
   In general it could be a two independent implementation


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org