chore: use OL macros instead of building OL ids from scratch #59197
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:providers
provider:databricks
provider:dbt-cloud
provider:snowflake
kacpermuda
force-pushed
the
chore-use-ol-macros
branch
from
c3e9551 to
3a88081
Compare
kacpermuda
force-pushed
the
chore-use-ol-macros
branch
from
3a88081 to
55812e9
Compare
mobuchowski
approved these changes
Dec 8, 2025
52 tasks
henry3260
pushed a commit
to henry3260/airflow
that referenced
this pull request
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some providers are building OpenLineage ids from scratch when emitting child events. Since we already require OL provider version in all of those cases for the function to run, we can switch to using OL macros, so that the ID generation logic stays only on OL provider. To make it happen I updated the required OL provider version from 2.3 to 2.5, since the root macro needed a fix that was included in 2.4.0 of OL provider and another from 2.5.0 here
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.