-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
Airflow unsupported pickle protocol while moving from Python 3.8 to Python 3.7 #14134
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
Update: destroying the Postgres db seems to fix the issue. Is there a way to migrate without dropping the entire DB? |
You need to find all the Columns in all tables that store a Pickled value and clear them. Example: clear the |
How do I find the Columns in the airflow tables that store a Pickled value? |
Do you mean truncate the whole table @kaxil ?
Meaning: UPDATE dag_run
SET conf = NULL ? Edit: by the way, I am getting this error without changing the Python version. |
I ran into this as well when upgrading. Ran @borismo's comment was helpful
Also had to drop some picked info in
|
@markhatch Thanks a lot for this answer. |
Is there a reason why pickle is being used to store information into the db? Seems like a proper way to cause upgrade issues... |
That's how tasks are serialized for celerry for example. So for example tasks can be retried if their fail to be executed. There are multiple reasons for that. But if you have a proposal how to get rid of it - feel free to discuss it in devlist or better - start a PR :) Airflow has > 2000 contributors so becoming one is a good idea. |
Apache Airflow version: 2.0.0
Environment: Python 3.7
What happened:
How to reproduce it:
It happened moving from Python 3.8 to Python 3.7
Anything else we need to know:
We are using Nomad + Docker to run Airflow, DBs used are Postgres and Redis
The issue is similar to #13317, I've already tried to clear the cookies and to change the address from which I use the web UI
The text was updated successfully, but these errors were encountered: