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

Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (JIRA)" <ji...@apache.org> on 2018/11/16 13:05:00 UTC

[jira] [Resolved] (AIRFLOW-251) Add optional parameter SQL_ALCHEMY_SCHEMA to control schema for metadata repository

     [ https://issues.apache.org/jira/browse/AIRFLOW-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ash Berlin-Taylor resolved AIRFLOW-251.
---------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

> Add optional parameter SQL_ALCHEMY_SCHEMA to control schema for metadata repository
> -----------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-251
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-251
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core
>            Reporter: Ed Parcell
>            Assignee: Iuliia Volkova
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Using SQL Server as a database for metadata, it is preferable to group all Airflow tables into a separate schema, rather than using dbo. I propose adding an optional parameter SQL_ALCHEMY_SCHEMA to control this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)