You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2019/10/18 15:57:22 UTC
[GitHub] [airflow] JonnyIncognito edited a comment on issue #6210:
[AIRFLOW-5567] BaseAsyncOperator
JonnyIncognito edited a comment on issue #6210: [AIRFLOW-5567] BaseAsyncOperator
URL: https://github.com/apache/airflow/pull/6210#issuecomment-543808908
> @JonnyIncognito I'm a gcp-er don't have aws access.
@jaketf I'm almost certainly going to write an operator that combines EmrAddStepsOperator and EmrStepSensor on top of your work once we figure out the state retention issue, so I'd be happy to contribute it to your PR as an example if you don't get to a GCP example first.
Question is what we're going to name this style of operators, related to the [other thread](https://github.com/apache/airflow/pull/6210#discussion_r335271755) about the class hierarchy and base naming. Options:
- Suffix to imply composition / doing more than one thing: XYZAsyncOperator vs. XYZAtomicOperator e.g. `Emr...StepsAsyncOperator` or `Emr...StepsAtomicOperator`
- How to imply action and sensing: RunXYZ vs. EnsureXYZ e.g. `EmrRunSteps...Operator` or `EmrEnsureSteps...Operator`
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services