[
https://issues.apache.org/jira/browse/AIRFLOW-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618921#comment-16618921
]
Jarek Potiuk commented on AIRFLOW-26:
-------------------------------------
We are working on implementation of Cloud Functions operators (AIRFLOW-2912) as
well as some basic Compute Engine (AIRFLOW-3078) very soon and it would be
great to align with the "future" consistent way. Currently we have separate
python file for separate operators (Delete/Deploy + Invoke in the future).
From what I understand from this issue and AIRFLOW-2056, preferred way is to
put together related "GC*" operators into single file (in our case they should
be named gcp_functions and gcp_compute respectively).
Is my understanding correct ?
> GCP hook naming alignment
> -------------------------
>
> Key: AIRFLOW-26
> URL: https://issues.apache.org/jira/browse/AIRFLOW-26
> Project: Apache Airflow
> Issue Type: Improvement
> Components: gcp
> 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
(v7.6.3#76005)
