[
https://issues.apache.org/jira/browse/AIRFLOW-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621799#comment-16621799
]
Jarek Potiuk commented on AIRFLOW-26:
-------------------------------------
Fine with 2.0. For breakup into sub-repositories. I am happy to help with the
migration then. I know I can find out more about it probably from past
discussions, but maybe you could shortly explain what's the foreseen timeline
for 2.0 / current 2.0 state shortly ?
I looked at [https://cwiki.apache.org/confluence/display/AIRFLOW]
documentation, and could not easily find anything more than 2.0 is "upcoming"
(there is quite a lot of outdated information there that should probably be
archived ;) BTW.). Maybe part of 2.0 should be some cleanup of the docs/JIRAS?
(if not planned already - I saw the separate discussion about Jira vs. Github
issues)? I will be happy to help with that later on as I like to have things
organised (but need to get more hang of Airflow by developing a number of
operators first).
> 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)
