kacpermuda opened a new pull request, #75133: URL: https://github.com/apache/airflow/pull/75133
Follow-up to #74752 and #75132, and stacked on both: only the last commit (`Describe loop reruns and expansion size in OpenLineage task events`) is new here. With #75132, OpenLineage events can carry everything needed to trace a task execution back from a single event, without reading the Airflow database: - `taskInstance.loop` groups the loop details: `group_id`, `index`, `max_iterations`, plus the loop `region_id`, `trajectory`, `forked_from_region_id` and `resumes_from_index` (which rerun of the loop an event comes from and what it replaced), and the gate's `decision`. This replaces the flat `loop_*` fields added in #74752, which haven't been released, so the loop details can later describe enclosing loops too. - `taskInstance.expanded_ti_count`: how many instances a mapped task's expansion has, so consumers know how many events to expect. - Worker events read the new public `RuntimeTaskInstance` attributes. Events for manual state changes get the same details from `get_task_instance_execution_position` instead of querying `dynamic_region`. Airflow 3.4 pre-releases without these fall back to what #74752 does. - A new guide documents how to identify a task execution from an event: run ids, every field, how each kind of task emits events, and grouping keys. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes (Claude Code) Generated-by: Claude Code (Opus 5.5) 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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
