[
https://issues.apache.org/jira/browse/AIRFLOW-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17222910#comment-17222910
]
Kamil Bregula commented on AIRFLOW-2075:
----------------------------------------
[~richard.williamson]
Hello,
We no longer use Jira for new tickets. Please, use Github Issue.
https://github.com/apache/airflow/issues
Jira is just an archive for old tickets. You can no longer create new tickets.
You can still comment on old tickets, but you can't expect a response. If the
ticket is important to you, please create a new ticket in Github Issue and give
the link to the Jira ticket.
Big love,
See:
https://issues.apache.org/jira/projects/AIRFLOW/issues/AIRFLOW-7120?filter=allopenissues
> 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)
