Add lineage_job_namespace and lineage_job_name OpenLineage macros #38829
Conversation
This file contains 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
kind:documentation
provider:openlineage
This was referenced Apr 8, 2024
dolfinus
force-pushed
the
feature/airflow-openlinage-new-macros
branch
from
b0dedc2
to
bb496fc
Compare
kacpermuda
reviewed
Apr 8, 2024
dolfinus
force-pushed
the
feature/airflow-openlinage-new-macros
branch
from
bb496fc
to
f03bd73
Compare
dolfinus
force-pushed
the
feature/airflow-openlinage-new-macros
branch
from
f03bd73
to
d8b3170
Compare
mobuchowski
approved these changes
Apr 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add new
lineage_job_namespace()andlineage_job_name(task_instance)macros to OpenLineage provider. Same as OpenLineage/OpenLineage#2582.Also updated macros documentation a bit.
^ 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 newsfragments.