feat: add OpenLineage support for BigQueryToBigQueryOperator #44214
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
provider:google
kacpermuda
force-pushed
the
feat-ol-bq-to-bq
branch
from
7b29013
to
eca79ba
Compare
Signed-off-by: Kacper Muda <[email protected]>
kacpermuda
force-pushed
the
feat-ol-bq-to-bq
branch
from
eca79ba
to
70c15ee
Compare
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.
This PR adds OpenLineage support for BigQueryToBigQueryOperator.
Within the operator itself, i removed the additional call to BQ API that got the job configuration as it's already returned by method that's submitting job - I adjusted the code to take advantage of that. The configuration returned is also saved as instance attribute for later use of OpenLineage method.
In the same time, I'm modifying two internal OpenLineage utils function:
get_facets_from_bq_tablenow do not return facets instead of returning empty facets when there is no schema or description for bq tableget_identity_column_lineage_facetis now checking if the source columns included in column lineage facet are actually in the schema of source datasets. It's now possible to generate this facet when source tables contain subset of columns of a destination table, which can be a case f.e. in BQ to BQ copy.^ 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.