Open Taragolis opened 11 months ago
Thanks for getting this set up!
@Taragolis i am happy to look into this Use base aws classes in AWS Glue Crawlers Operators/Sensors/Triggers
? or anyone is working already?
@Taragolis I am happy to take EMR, EC2 and S3 (operators) here
@vincbeck @eladkal Working on this Use base aws classes in AWS Glue Data Catalog Sensors
didnt find anything in the documentation and example code for this. Planning to add them here https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/operators/glue.html is this fine?
@vincbeck @eladkal Working on this
Use base aws classes in AWS Glue Data Catalog Sensors
didnt find anything in the documentation and example code for this. Planning to add them here https://airflow.apache.org/docs/apache-airflow-providers-amazon/stable/operators/glue.html is this fine?
Please yes :)
@gopidesupavan do you plan to address the other Glue services that were left?
@eladkal Yes will update other services, coming week.
Body
Right now some inconsistency exists between different Operators/Sensors/Triggers which are use
AwsBaseGeneric
hook. After #34784 and #34884 we could make all of them (except Transfer Operators) use same subset of generic attributes.It might make more easier to end users use this objects (don't need to think is it
region
orregion_name
or is it even support this arguments), as well as make easier extend by new new hook parameters to all this operators in the one go.General Approach for solve each case:
AwsBaseOperator
for operators,AwsBaseSensor
for sensors. In some very specific case e.g. multi inheritance required to useAwsBaseHookMixin
(see: AppflowRecordsShortCircuitOperator)AwsBaseWaiterTrigger
(if required)All this steps already done for some of the operators, so it could be use as a reference
Committer