dabla commented on PR #38707:
URL: https://github.com/apache/airflow/pull/38707#issuecomment-2048968598

   > > Yes I saw that and I have same issue I think with MSGraphOperator but I 
don't fully understand how I can fix this :(
   > 
   > Simply - You can't use code from `airfliow` in providers until the 
provider has `apache-airflow>=NEXT_MINOR` - until then the provider must have a 
"polyfill" - i.e. catch import error and have the same code that is in the 
provider that providers same functionality when provider is installed on 
airflow < NEXT_MINOR. With a note to remove it when min-airflow version is >= 
NEXT_MINOR (we have a policy for bumping - in two weeks we increase 
min-airflow-version to 2.7.0, so after that any code that was there fore < 2.7 
can be removed from providers.
   > 
   > For SQL providers, a simpler way around it is to add a code to common.sql 
as a new feature and use `apache-airfow-provider-common-sql >= in 
`provider.yaml` - but then it should be visibly marked as added in common.sql 
x.y.z (via since flag in the docuemntation).
   > 
   > There was a discussion to have `common.util` provider at some point of 
time but it stalled a bit. Maybe we should come back to it.
   
   Ok got it, thank you for the explantion, indeed I saw that discussion of the 
common.util.


-- 
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]

Reply via email to