[
https://issues.apache.org/jira/browse/AIRFLOW-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16620378#comment-16620378
]
Jarek Potiuk commented on AIRFLOW-26:
-------------------------------------
Wow. I see now that it's all about separate repos and modules split-off Airflow
main project. I guess It is not yet finalised exactly how to approach it and no
rules are established - it's rather fresh discussion, possibly it will be to
early to switch to it now (but I am happy to take part in moving as soon as the
community converges). There are a couple of issues that I see now (such as
using some of the airflow's classes/objects in the operator - for example
LoggingMixin - this would complicate the dependency management somehow - this
should be linked to release schedule of Airflow and airflow will have to be a
dependency (and then the modules would have to have dependencies on particular
versions of airflow. It's a bit too early for me to decide, as I am super-fresh
in Airflow.
For me looks like the best approach fior now will be to just combine those
operators into single "gcp_functions.py" operator in contrib for now and deal
with repo separation when we have clear decision on how to progress (I might
even be happy at some point in time to coordinate that but it's definitely too
early for that for me)
[~fenglu] - what do you think?
> 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)
