You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ed Parcell (JIRA)" <ji...@apache.org> on 2016/06/17 00:45:05 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15335105#comment-15335105 ]
Ed Parcell commented on AIRFLOW-251:
------------------------------------
I created a pull request for this issue: https://github.com/apache/incubator-airflow/pull/1600
> 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)