Skip to content

add clear_number to OpenLineage's dagrun-level event run id generation - #44617

Merged
mobuchowski merged 1 commit into
mainfrom
clear-run-id
Dec 7, 2024
Merged

add clear_number to OpenLineage's dagrun-level event run id generation#44617
mobuchowski merged 1 commit into
mainfrom
clear-run-id

Conversation

@mobuchowski

Copy link
Copy Markdown
Contributor

Right now, when task gets cleared via UI, and dag run gets scheduled again, the OpenLineage integration will emit the event with same OL run_id as in the first execution. This is confusing for OpenLineage consumers, as the run that's already received terminal state should not receive following events.

To fix that, use clear_number introduced in Airflow 2.8.0 as additional information used in generating OpenLineage's run_id to distinguish between those runs.

Signed-off-by: Maciej Obuchowski <obuchowski.maciej@gmail.com>
@mobuchowski
mobuchowski merged commit e26909d into main Dec 7, 2024
@potiuk
potiuk deleted the clear-run-id branch January 11, 2025 19:43
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
apache#44617)

Signed-off-by: Maciej Obuchowski <obuchowski.maciej@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants