-
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
BigqueryToGCS Operator Failing #24364
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Thank you @gmyrianthous . This helps. In our case we are not managing the libraries in composer. We are letting composer manage the libraries. Hope this is brought into composer 2.0.14, else we might have to explicitly mention this and provide extra care while upgrading our composer environment. EDIT: We upgraded from 2.0.8 to 2.0.14 since 2.0.8 was having some known issues that would be fixed end of this quarter and is affecting our production. |
@adityaprakash-bobby This isn't fixed in composer |
@eladkal Is it wise to override the composer managed airflow python packages? I see composer 2.0.14 till the latest 2.0.16, has the apache-airflow-providers-google==2022.5.18+composer package. |
That is a question for Composer support. |
Sure, have let it open for support with Composer. Thanks Elad! |
Related |
Closind with #24461 |
Apache Airflow Provider(s)
google
Versions of Apache Airflow Providers
apache-airflow-providers-google==2022.5.18+composer
Apache Airflow version
2.2.3
Operating System
Managed
Deployment
Composer
Deployment details
Environment Configuration:
Workload configuration:
Core Infrastructure:
Configuration Overrides:
No Airflow configuration overrides
What happened
Previously we were on apache-airflow-providers-google==6.4.0 (composer - 2.0.8 | airflow - 2.2.3) in which we were using the BigqueryToGCS operator in our DAGs as follows:
This was working until we switched to apache-airflow-providers-google==2022.5.18+composer (composer - 2.0.14 | airflow - 2.2.3).
Now every time the operator is executed, the task goes to fail state in airflow. However, I observed that the CSV files are created as expected from the operator. What the logs state is that the operator is not able to find the bigquery job it executed, hence fails. Task logs are follows:
I am also not able to install the package apache-airflow-providers-google==2022.5.18+composer locally as
pip
is not able to locate this, nor am I able to see it in the releases.What you think should happen instead
The task should be completed with a success status given the query is all right and executes.
How to reproduce
No response
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: