airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (AIRFLOW-2870) Migrations fail when upgrading from below cc1e65623dc7_add_max_tries_column_to_task_instance
Date Wed, 08 Aug 2018 11:21:00 GMT


ASF GitHub Bot commented on AIRFLOW-2870:

bolkedebruin opened a new pull request #3720: [AIRFLOW-2870] Use abstract TaskInstance for
   Make sure you have checked _all_ steps below.
   ### Jira
   - [X] My PR addresses the following [Airflow Jira](
issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - In case you are fixing a typo in the documentation you can prepend your commit with
\[AIRFLOW-XXX\], code changes always need a Jira issue.
   ### Description
   - [X] Here are some details about my PR, including screenshots of any UI changes:
   If we use the full model for migration it can have columns
   added that are not available yet in the database. Using
   an abstraction ensures only the columns that are required
   for data migration are present.
   ### Tests
   - [X] My PR adds the following unit tests __OR__ does not need testing for this extremely
good reason:
   Db migration
   ### Commits
   - [X] My commits all reference Jira issues in their subject lines, and I have squashed
multiple commits if they address the same issue. In addition, my commits follow the guidelines
from "[How to write a good git commit message](":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   @ashb @gwax PTAL
   ### Documentation
   - [ ] In case of new functionality, my PR adds documentation that describes how to use
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   ### Code Quality
   - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> Migrations fail when upgrading from below cc1e65623dc7_add_max_tries_column_to_task_instance
> --------------------------------------------------------------------------------------------
>                 Key: AIRFLOW-2870
>                 URL:
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: George Leslie-Waksman
>            Priority: Blocker
> Running migrations from below fail
> {noformat}
> INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
> INFO  [alembic.runtime.migration] Will assume transactional DDL.
> INFO  [alembic.runtime.migration] Running upgrade 127d2bf2dfa7 -> cc1e65623dc7, add
max tries column to task instance
> Traceback (most recent call last):
>   File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/", line 1182,
in _execute_context
>     context)
>   File "/usr/local/lib/python3.6/site-packages/sqlalchemy/engine/", line 470,
in do_execute
>     cursor.execute(statement, parameters)
> psycopg2.ProgrammingError: column task_instance.executor_config does not exist
> LINE 1: ...ued_dttm, AS task_instance_pid, task_insta...
> {noformat}
> The failure is occurring because
imports TaskInstance from the current code version, which has changes to the task_instance
table that are not expected by the migration.
> Specifically, adds an executor_config
column that does not exist as of when
is run.
> It is worth noting that this will not be observed for new installs because the migration
branches on table existence/non-existence at a point that will hide the issue from new installs.

This message was sent by Atlassian JIRA

View raw message