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

Posted to commits@airflow.apache.org by "Richard Williamson (Jira)" <ji...@apache.org> on 2020/10/24 12:37:00 UTC

[jira] [Commented] (AIRFLOW-2075) Extract and create a data access layer

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

Richard Williamson commented on AIRFLOW-2075:
---------------------------------------------

Can we re-open the more general version of this request to get Airflow 2 to work with Spanner by either sqlalchemy support or any other means?  Making Airflow 2.0 work with Spanner would allow multi-region support by running a scheduler in 2 or more regions using Airflow 2.0 HA features.

> Extract and create a data access layer
> --------------------------------------
>
>                 Key: AIRFLOW-2075
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-2075
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.0.0
>            Reporter: Yang Pan
>            Priority: Major
>
> Currently Airflow is tightly coupled with sqlalchemy. 
> [https://github.com/search?p=2&q=%22from+sqlalchemy%22+repo%3Aapache%2Fincubator-airflow+path%3A%2Fairflow&type=Code&utf8=%E2%9C%93]
> While it's convenient for sqlalchemy compatible database, it makes non compatible ones, such as google cloud spanner, harder to integrate.
> It would be nice if the data access layer can be decoupled from the airflow core, and developers have option to use sqlalchemy or swap to talk to db directly.



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