[
https://issues.apache.org/jira/browse/AIRFLOW-2268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
sulphide updated AIRFLOW-2268:
------------------------------
Description:
if upgradedb fails in the middle and you try to run it again you can receive
fatal errors, e.g.:
(from upgradedb for airflow 1.9)
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1060,
"Duplicate column name 'max_tries'") [SQL: u"ALTER TABLE task_instance ADD
COLUMN max_tries INTEGER DEFAULT '-1'"]
solution: make upgradedb idempotent by using transactions that rollback on
failure.
was:
if upgradedb fails in the middle and you try to run it again you can receive
fatal errors, e.g.:
(from upgradedb for airflow 1.9)
sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1060,
"Duplicate column name 'max_tries'") [SQL: u"ALTER TABLE task_instance ADD
COLUMN max_tries INTEGER DEFAULT '-1'"]
solution, make upgradedb idempotent by using transactions that rollback on
failure.
> upgradedb is not idempotent
> ---------------------------
>
> Key: AIRFLOW-2268
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2268
> Project: Apache Airflow
> Issue Type: Bug
> Affects Versions: 1.9.0
> Reporter: sulphide
> Priority: Major
>
> if upgradedb fails in the middle and you try to run it again you can receive
> fatal errors, e.g.:
> (from upgradedb for airflow 1.9)
> sqlalchemy.exc.OperationalError: (_mysql_exceptions.OperationalError) (1060,
> "Duplicate column name 'max_tries'") [SQL: u"ALTER TABLE task_instance ADD
> COLUMN max_tries INTEGER DEFAULT '-1'"]
> solution: make upgradedb idempotent by using transactions that rollback on
> failure.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
