You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kamil Bregula (JIRA)" <ji...@apache.org> on 2019/06/11 14:04:00 UTC
[jira] [Updated] (AIRFLOW-4152) dataflow hook should take project
from the connection id
[ https://issues.apache.org/jira/browse/AIRFLOW-4152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kamil Bregula updated AIRFLOW-4152:
-----------------------------------
Component/s: gcp
> dataflow hook should take project from the connection id
> --------------------------------------------------------
>
> Key: AIRFLOW-4152
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4152
> Project: Apache Airflow
> Issue Type: Improvement
> Components: gcp
> Reporter: Ben Marengo
> Priority: Major
>
> following AIRFLOW-1401, where concerns were raised about the inconsistency of the dataflow hook / operators but never resolved, we should unify the dataflow hook / operators to take project id from connection id, like every other gcp hook/operator
> this will probably involve a backward incompatible change (where the {{project}} key can no longer be passed in the {{variables}} dictionary to methods {{DataFlowHook.start_<job-type>_dataflow()}})
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)