potiuk commented on PR #44809: URL: https://github.com/apache/airflow/pull/44809#issuecomment-2567026175
> @potiuk Okay but this would then have an impact on imports no? Or would you keep same structure as is and move the GenericTransfer from standard providers to common sql? Generic Transfer has **only** been moved to "standard" provider recently as part of the preparation for Airflow 3. And the "standard" provider is not YET released in a `1.0.*` version - it is 0.0.3 now - because we have not completed yet extraction of everything there, and we expected that we might have some changes here and there, so Generic Transfer moved to the standard provider can be classified as mistake - should be moved to common.sql in the first place, and we can do it without taking care about back-compatibility. The only back-compatibiity issue is that the old generic transfer should be redirected in Airflow 3 - but we can simply redirect it to the new place in common.sql, no problem with it whatsoever: * https://github.com/apache/airflow/blob/main/airflow/operators/__init__.py#L45 -- 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]
