airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3266) AWS Athena Operator in Airflow
Date Sun, 28 Oct 2018 10:11:00 GMT

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

ASF GitHub Bot commented on AIRFLOW-3266:
-----------------------------------------

phani8996 opened a new pull request #4111: [AIRFLOW-3266] AWS Athena Operator and hook created
URL: https://github.com/apache/incubator-airflow/pull/4111
 
 
   ### Jira
   - [x] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. For example, "\[AIRFLOW-3266\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-3266
   
   ### Description
   
   - [x] There is no official athena operator as of now airflow. Either one has do it using
boto3 in python operator or using aws cli in bash operator. Either of these does not take
care of total life cycle of query. Create a Athena operator and hook to submit presto query
and update task based of state of submitted query.
   
   ### Tests
   
   - [ ] I added test to assert query parameters. Unfortunately library `moto` which used
for unit testing aws services does not support at this point of time.
   
   ### Commits
   
   - [x] My commits all reference Jira issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use
it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   
   ### Code Quality
   
   - [x] Passes `flake8`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> AWS Athena Operator in Airflow
> ------------------------------
>
>                 Key: AIRFLOW-3266
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3266
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: aws
>    Affects Versions: 1.10.0
>            Reporter: Sai Phanindhra
>            Assignee: Sai Phanindhra
>            Priority: Minor
>
> There is no official athena operator as of now airflow. Either one has do it using boto3
in python operator or using aws cli in bash operator. Either of these does not take care of
total life cycle of query. Create a Athena operator and hook to submit presto query and update
task based of state of submitted query.



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

Mime
View raw message