This is an automated email from the ASF dual-hosted git repository. utkarsharma pushed a commit to branch v2-9-test in repository https://gitbox.apache.org/repos/asf/airflow.git
commit 5d5d21a483d06e241ac655dd0f38ee35ac263ef2 Author: Marek Hanuš <[email protected]> AuthorDate: Mon Jun 24 17:18:47 2024 +0200 docs: fix typo in upgrading.rst (#40399) (cherry picked from commit 3133c33684d6fc97842e697c65746da11a690c08) --- docs/apache-airflow/installation/upgrading.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apache-airflow/installation/upgrading.rst b/docs/apache-airflow/installation/upgrading.rst index 5ab8100287..67f18534e9 100644 --- a/docs/apache-airflow/installation/upgrading.rst +++ b/docs/apache-airflow/installation/upgrading.rst @@ -35,7 +35,7 @@ Upgrade preparation - make a backup of DB It is highly recommended to make a backup of your metadata DB before any migration. If you do not have a "hot backup" capability for your DB, you should -do it after shutting down your Airflow instances, so that the backup of is consistent. +do it after shutting down your Airflow instances, so that the backup of your database will be consistent. If you did not make a backup and your migration fails, you might end-up in a half-migrated state and restoring DB from backup and repeating the migration might be the only easy way out. This can for example be caused by a broken
