dstandish commented on PR #31712: URL: https://github.com/apache/airflow/pull/31712#issuecomment-1611853368
It's possible to have it both ways I suppose. You could introduce the base class in core. Then we could duplicate it into a `compat` module in each provider as a fallback if user's airflow is old. And then we could set it for removal from provider once provider min airflow version is sufficient. However, using class or interface *just* for the purpose of recordkeeping does feel wrong. Feels like class structure should be driven by other concerns. And maybe it's merited on that score anyway, dunno. But alternatively we can possibly add an attr on base operator such as `supports_defer` or some meta tag in docstring perhaps that can be used for this purpose. -- 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]
