-
Notifications
You must be signed in to change notification settings - Fork 14.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BigQueryInsertJobOperator broken for some kinds of query jobs #24535
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
the fix is in apache-airflow-providers-google 8.0.0 |
CC: @lwyszomi (not sure @raphaelauv if it's fixed) |
( I'm only speaking about 8.0.0 , not about current main branch ) |
In my PR this problem should be fixed, please check https://github.com/apache/airflow/pull/24416/files#diff-529929b4ca60ce73b8da0f45d8a5c43c2d4e391b913fe78b39892899f812951eR2171 we checking if |
As explained issue is fixed please bump provider version to 8.0.0 |
Great thank you! |
Apache Airflow Provider(s)
google
Versions of Apache Airflow Providers
I'm using a google composer managed version
apache-airflow-providers-google==2022.5.18+composer
but I see the issue in code in master as wellApache Airflow version
2.2.5
Operating System
cloud composer
Deployment
Composer
What happened
Some of my BigQueryInsertJobOperator query jobs started failing following the update of composer which updated google provider from
apache-airflow-providers-google==6.3.0
to
apache-airflow-providers-google==2022.5.18+composer
I'm not sure what they are exactly using since the version is now hidden...
Although I was able to see a code path producing the bug in master.
It happens when BigQueryInsertJobOperator is used to build a query job and no destination table is given. It is allowed doc
But in current master code added by this PR always expects
desinationTable
to be filled for a query job. The PR didn't introduce the bug though it was trying to fix the same bug from a previous PR. It just wrongly assumed that the field is always present.Essentially #23826 has not been completely fixed.
I'm willing to send a PR but I basically discovered the concepts of links reading the code while debugging this and I'm not sure how to disable the link for query jobs without destination tables. I guess It could also link to the temporary table but that's not very useful as the temporary table gets cleaned quickly.
What you think should happen instead
The
BigQueryInsertJobOperator
operator should not crash whendesinationTable
is not filled for a query jobHow to reproduce
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: