You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "r-magalhaes (via GitHub)" <gi...@apache.org> on 2026/01/14 12:02:09 UTC
[D] Airflow 3 migration db clean [airflow]
GitHub user r-magalhaes created a discussion: Airflow 3 migration db clean
Hello,
I'm in the process of upgrading from Airflow 2.x to Airflow 3.1.5 and I've followed the Airflow 3 Migration documentation and it left me a questions. On the step where it says we should run a airflow db clean before actually upgrading, is there any particular table that needs to be cleaned or is it supposed to be a full clean?
My question comes because if it's a full clean then I lose dag run data that I have to keep.
I run Airflow in a Kubernetes cluster and deploy it via Helm Chart.
GitHub link: https://github.com/apache/airflow/discussions/60516
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Airflow 3 migration db clean [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
GitHub user potiuk added a comment to the discussion: Airflow 3 migration db clean
Up to you. The clean recommendation is there in order to speed up the migration - you as Deployment Manager should choose how much of the old data is cleaned and which data you want to keep.
GitHub link: https://github.com/apache/airflow/discussions/60516#discussioncomment-15498803
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org
Re: [D] Airflow 3 migration db clean [airflow]
Posted by "r-magalhaes (via GitHub)" <gi...@apache.org>.
GitHub user r-magalhaes edited a discussion: Airflow 3 migration db clean
Hello,
I'm in the process of upgrading from Airflow 2.x to Airflow 3.1.5 and I've followed the Airflow 3 Migration documentation and it left me a question. On the step where it says we should run a airflow db clean before actually upgrading, is there any particular table that needs to be cleaned or is it supposed to be a full clean?
My question comes because if it's a full clean then I lose dag run data that I have to keep.
I run Airflow in a Kubernetes cluster and deploy it via Helm Chart.
GitHub link: https://github.com/apache/airflow/discussions/60516
----
This is an automatically sent email for commits@airflow.apache.org.
To unsubscribe, please send an email to: commits-unsubscribe@airflow.apache.org