airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Riccomini (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (AIRFLOW-26) GCP hook naming alignment
Date Mon, 02 May 2016 23:49:12 GMT

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

Chris Riccomini edited comment on AIRFLOW-26 at 5/2/16 11:48 PM:
-----------------------------------------------------------------

This might have a merge conflict with AIRFLOW-31, as AIRFLOW-31 is changing how imports are
done. Should be minor, but just a heads-up. Specifically, [here|https://github.com/airbnb/airflow/pull/1272/files#diff-a32a363fa616685db3bfefba947535b2R558].


was (Author: criccomini):
This might have a merge conflict with AIRFLOW-31, as AIRFLOW-31 is changing how imports are
done. Should be minor, but just a heads-up.

> GCP hook naming alignment
> -------------------------
>
>                 Key: AIRFLOW-26
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-26
>             Project: Apache Airflow
>          Issue Type: Improvement
>            Reporter: Alex Van Boxel
>            Assignee: Alex Van Boxel
>            Priority: Minor
>              Labels: gcp
>
> Because we have quite a few GCP services, it's better to align the naming to not confuse
new users using Google Cloud Platform:
> gcp_storage > renamed from gcs
> gcp_bigquery > renamed from bigquery
> gcp_datastore > rename from datastore
> gcp_dataflow > TBD
> gcp_dataproc > TBD
> gcp_bigtable > TBD
> Note: this could break 'custom' operators if they use the hooks.
> Can be assigned to me.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message