e-galan commented on PR #39752:
URL: https://github.com/apache/airflow/pull/39752#issuecomment-2127281714

   > There is no clear what we try to achieve here. Deprecate or Remove 
functional because there is not available in upstream service? There is quite a 
different between two of them
   > 
   > If we deprecate something, than we keep it as is with just a warning until 
one of option happen
   > 
   > * Finally removed in upstream service / protocol / library
   > * We decide that is a good time to release a major version of provider for 
avoid maintenance hell ( cc: @eladkal Maybe it is a good time to release new 
major version of Google provider, there is a lot of deprecations from Airflow 
1.10)
   > 
   > If there is not available anymore, we could raise an error, with clear 
reason why it removed. "This not working anymore due to sunset of service XXX 
please use YYY"
   
   @Taragolis I think we're trying to remove the operators, but I was led to 
believe that we can't just remove it without giving the users some time and 
hints about the alternatives.  
   
   The exceptions that I placed in the __init__method of the operators should 
do just that - they inform the users that the operators can no longer be 
supported, and suggests an alternative operator, if it exists. 


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