You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Axel Goblet (Jira)" <ji...@apache.org> on 2019/11/14 14:43:00 UTC

[jira] [Created] (AIRFLOW-5933) Unable to define schema for alembic version table

Axel Goblet created AIRFLOW-5933:
------------------------------------

             Summary: Unable to define schema for alembic version table
                 Key: AIRFLOW-5933
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5933
             Project: Apache Airflow
          Issue Type: Improvement
          Components: database
    Affects Versions: 1.10.6, 2.0.0
            Reporter: Axel Goblet


Airflow allows defining the database schema used by SQL alchemy via the sql_alchemy_schema setting in the core section of the config. Alembic does not use this schema for its version table, and will always use the version table in the default schema.

To be able to host multiple airflow instances in 1 database (split across schemas), one should be able to specify the schema where the alembic version table is placed in as well.

The fix for this is described in this stack overflow article: [https://stackoverflow.com/questions/42316280/how-to-specific-table-schema-for-alembic-version-when-using-flask-migrate]

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)