xBis7 opened a new pull request, #68082:
URL: https://github.com/apache/airflow/pull/68082
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
This PR is adding a listener under the Kafka provider which provides an
implementation for the DagRun and TaskInstance state change event hooks.
The listener publishes a message to a pre-existing Kafka topic for every
event. Each message has some extra metadata for the dag or task that the event
belongs to.
DagRun events and TaskInstance events are separated and guarded behind
different config flags. Both flags are disabled by default because each
listener adds load to Airflow that users might not want.
The listener expects that the user has already created the topic and then
defines it in the listener's config section. In case the topic doesn't exist,
the listener doesn't fail. Instead it logs a warning and checks for the topic
existence again after a configured interval.
Users can also filter events for dag runs based on dag_id and for tasks
based on dag_id + task_id. For example, someone could choose to get only dag
run state events for a particular dag and nothing else.
By adding a listener to the provider we can have dags consume from the Kafka
topic and react to messages. When a particular message arrives, a deferred task
could be triggered. This could also work for dags across multiple Airflow
installations, all sharing the common topic. For that reason, I also added a
`source` config key, so that users can distinguish where the messages came from.
## Testing
I've added unit tests and also a simple integration test that uses an actual
broker. I've also tested the changes manually.
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [X] Yes (please specify the tool below)
Claude Code, Opus 4.7
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
