atharv9017 opened a new issue, #45838:
URL: https://github.com/apache/airflow/issues/45838

   ### Apache Airflow version
   
   2.10.4
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   The following classes subclass airflow.models.skipmixin.SkipMixin, which 
directly accesses the DB:
   
   BranchMixIn (used in BaseBranchOperator, BranchPythonOperator, 
BranchDateTimeOperator, LatestOnlyOperator, etc.)
   BaseSensorOperator
   BranchSQLOperator
   ShortCircuitOperator
   These operators need to be refactored to work with Task SDK, as the current 
implementation directly accesses the database. The operations should be routed 
to the API server from the worker instead of the current DB access.
   
   ### What you think should happen instead?
   
   Remove the inheritance of these operators from SkipMixin.
   Route the DB-related operations to the API Server from the worker.
   
   ### How to reproduce
   
   Use any of the affected operators (e.g., BaseBranchOperator, 
BranchPythonOperator, etc.).
   Observe that DB operations are being performed directly by the operators, 
causing a dependency on DB access in the Task SDK context.
   
   ### Operating System
   
   Windows
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   _No response_
   
   ### Anything else?
   
   This issue occurs whenever the affected operators are used, causing issues 
with Task SDK integration due to direct DB access.
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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