potiuk commented on issue #27292: URL: https://github.com/apache/airflow/issues/27292#issuecomment-1454842888
Not only thoughts. There is an issue for actually spliting the provider : https://github.com/apache/airflow/issues/15933 - but this one is complex because of common parts so maintaining such split provider would be difficult to maintain (we learned a lot about it when we added `common.sql`. However- when it comes to extras, it could be a better solution indeed, I have not thought about it, but it might actually make it much easier for users and would let us pick and choose which extras in google provider we might want to have enabled for which python versions. We already even have AirflowOptionalProviderFeatureException which would be nice in this case - we could throw appropriate error explaining that this and that extra is needed for this and that module. I **think** I like the idea better than splitting the provider. But I have to think a bit about it, from the first glance it looks like an easy solution to this problem. -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
