You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Jarek Potiuk (Jira)" <ji...@apache.org> on 2019/11/14 16:42:00 UTC
[jira] [Resolved] (AIRFLOW-5768) Google Cloud SQL - Don't store
ephemeral connection object to database
[ https://issues.apache.org/jira/browse/AIRFLOW-5768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jarek Potiuk resolved AIRFLOW-5768.
-----------------------------------
Fix Version/s: 2.0.0
Resolution: Fixed
> Google Cloud SQL - Don't store ephemeral connection object to database
> ----------------------------------------------------------------------
>
> Key: AIRFLOW-5768
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5768
> Project: Apache Airflow
> Issue Type: Improvement
> Components: gcp
> Affects Versions: 1.10.5
> Reporter: Daniel Standish
> Assignee: Daniel Standish
> Priority: Major
> Fix For: 2.0.0
>
>
> GCP cloud sql operator creates dynamically an ephemeral Connection object. It persists to metastore during execution and deletes afterward.
> This behavior has negative impact on our ability to refactor creds management.
> By not persisting to database, we can also remove some complexity re ensuring connection is deleted in event of failure, and the tests that go along with that.
> This change requires that we add optional param `connection` to both MySqlHook and PostgresHook.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)