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_table now do not return facets instead of returning empty facets when there is no schema or description for bq table
get_identity_column_lineage_facet is 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.rst or {issue_number}.significant.rst, in newsfragments.
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.