eladkal commented on issue #20139: URL: https://github.com/apache/airflow/issues/20139#issuecomment-993227095
> Since we are making these changes and going to be deprecating old operators in favor of new ones, it may be a good time to address some standardization issues as well? Two that have bugged me a bit are acronym capitalization across the Operators, and whether to prefix them all with `AWS` or not. > > These are incomplete lists just for example: we have `SnsPublishOperator` but we capitalize the acronyms in `SQSPublishOperator` and `ECSOperator`. We prefix `AwsGlueCrawlerOperator` and `AwsBatchOperator` in lowercase, `AWSAthenaOperator` is prefixed in uppercase, and no prefix at all on `GlacierCreateJobOperator` or `CloudFormationCreateStackOperator` The instructions are listed in AIP 21 cases 3-4 and case 6. https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-21%3A+Changes+in+import+paths#AIP21:Changesinimportpaths-Case#3{aws/azure/gcp}_* https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-21%3A+Changes+in+import+paths#AIP21:Changesinimportpaths-Case#6Otherisolatedcases The sensors/operators classes names should not have Aws/AWS as part of the class name. So: `SnsPublishOperator` -> No change `SQSPublishOperator` -> `SqsPublishOperator` `AwsBatchOperator` -> `BatchOperator` `AWSAthenaOperator` -> `AthenaOperator` etc... @ferruzzi would you like to work on it? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
