[
https://issues.apache.org/jira/browse/AIRFLOW-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16825127#comment-16825127
]
Feng Lu commented on AIRFLOW-1894:
----------------------------------
[~jackjack10] The newly added GCP operators try to use the new client libraries
as much as they can and fall back to the old ones only when absolutely needed.
As [~kaxilnaik] mentioned, we also need to retrofit existing operators (e.g.,
BigQuery, DataProc) with new client libraries as they become available.
> Rebase and migrate existing Airflow GCP operators to google-python-cloud
> ------------------------------------------------------------------------
>
> Key: AIRFLOW-1894
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1894
> Project: Apache Airflow
> Issue Type: Improvement
> Components: contrib
> Affects Versions: 2.0.0
> Reporter: Feng Lu
> Assignee: Feng Lu
> Priority: Minor
>
> [google-api-python-client|https://github.com/google/google-api-python-client]
> is in maintenance mode and it's recommended that
> [google-cloud-python|https://github.com/GoogleCloudPlatform/google-cloud-python]
> should be used whenever possible. Given that we don't have feature parity
> between the two libraries, this issue is created to track the long-term
> migration efforts moving from google-api-python-client to
> google-cloud-python. Here are some general guidelines we try to follow in
> this cleanup process:
> - add google-cloud-python dependency as part of gcp_api extra packages (make
> sure there is no dependency conflict between the two).
> - new operators shall be based on google-cloud-python if possible.
> - migrate existing GCP operators when the underlying GCP service is available
> in google-cloud-python.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
