-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
2.2.3 -> 2.3 upgrade db error with mysql metadb #23605
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
So, currently unable to move to v.2.3. |
I can confirm that we are experiencing the same issue outlined above. |
I had the same problem
it seems to me that the query should be generated as below
I wonder if the problem concerns version 5.7 ? |
Probably we can work around this by explicitly joining |
so, it'll be released in v.2.3.1, right? |
Correctl v2-3-test is there for cherry-picking changes from |
Closing as should be fixed by #23528 |
Apache Airflow version
2.3.0 (latest released)
What happened
Hi,
Tried to upgrade from v.2.2.3 to v.2.3
airflow upgrade db:
The above mysql statement, which causes error, seems to be generated in the count(self) function in /sqlalchemy/orm/query.py.
I ran that statement through mysql workbench and it's easy to see that it's wrong
There is no the rendered_task_instance_fields table in the FROM clause.
I probably know how to fix the statement but the mysql code is autogenerated (am I right?) but not hardcoded.
What you think should happen instead
No response
How to reproduce
airflow db upgrade --show-sql-only
to check the changes. Everything's fine.airflow db upgrade
Operating System
Oracle Linux 7.8
Versions of Apache Airflow Providers
No response
Deployment
Virtualenv installation
Deployment details
MySQL DB 5.7.10 which is supported per the docs.
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: