Re: Inconsistent class names for AWS integrations

2019-11-01 Thread MinJae Kwon
py:SQSSensor -> > ./providers/aws/sensors/sqs.py:SQSSensor > ./providers/aws/sensors/athena.py:AthenaSensor -> > ./providers/aws/sensors/athena.py:AthenaSensor > ./sensors/s3_key_sensor.py:S3KeySensor -> > ./providers/aws/sensors/s3.py:S3KeySensor > ./sensors/s3_prefix_se

Re: Inconsistent class names for AWS integrations

2019-10-31 Thread MinJae Kwon
py:SQSSensor -> > ./providers/aws/sensors/sqs.py:SQSSensor > ./providers/aws/sensors/athena.py:AthenaSensor -> > ./providers/aws/sensors/athena.py:AthenaSensor > ./sensors/s3_key_sensor.py:S3KeySensor -> > ./providers/aws/sensors/s3.py:S3KeySensor > ./sensors/s3_prefix_se

Inconsistent class names for AWS integrations

2019-10-29 Thread MinJae Kwon
Hi all. While I was working on AIRFLOW-5803, I found there are inconsistencies between class names for each AWS operators/hooks. For example, Athena hook is named as 'AWSAthenaHook', but Dynamodb hook is named as 'AwsDynamoDBHook', and S3 hook is just 'S3Hook' (So, AIRFLOW-5803 is trying to re