airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ed Parcell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-251) Add optional parameter SQL_ALCHEMY_SCHEMA to control schema for metadata repository
Date Wed, 20 Jul 2016 20:55:21 GMT

    [ https://issues.apache.org/jira/browse/AIRFLOW-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15386604#comment-15386604
] 

Ed Parcell commented on AIRFLOW-251:
------------------------------------

I have updated the pull request. Unit tests and code quality now pass.

> 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
>    Affects Versions: Airflow 2.0
>            Reporter: Ed Parcell
>            Priority: Minor
>
> 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
(v6.3.4#6332)

Mime
View raw message