mobuchowski commented on issue #40735:
URL: https://github.com/apache/airflow/issues/40735#issuecomment-2269087241
@wslulciuc Looked at this some time ago.
Natural approach to do this would be to add listener calls to API endpoints
(or, somewhere deeper that eventually modifies database) and call it a day.
However:
- API operates on different objects than current listener - it operates
directly on DB (SQLAlchemy) objects instead of creating for example DagRun etc
objects
- There are more than single API calls to do that one thing. It seems one
is for UI, second is for regular API.
- There is unclear what we should do with "followup tasks". Airflow can
react to completed or failed DAG or Task with scheduling other things, or
failing them. Should we manually issue "empty" events for them?
- When we complete or fail task manually, we don't actually get the same
information that we got from inside worker.
- The whole mechanism will completely change for Airflow 3 anyway due to
AIP-72.
I think we should work on this as part of AIP-72. I don't think there's good
workaround for that unfortunately.
--
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]
