[
https://issues.apache.org/jira/browse/AIRFLOW-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16446654#comment-16446654
]
ASF subversion and git services commented on AIRFLOW-2326:
----------------------------------------------------------
Commit f520990fe0b7a70f80bec68cb5c3f0d41e3e984d in incubator-airflow's branch
refs/heads/master from [~b11c]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=f520990 ]
[AIRFLOW-2326][AIRFLOW-2222] remove contrib.gcs_copy_operator
Closes #3232 from berislavlopac/AIRFLOW-2326
> Duplicate GCS copy operator
> ---------------------------
>
> Key: AIRFLOW-2326
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2326
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Berislav Lopac
> Assignee: Berislav Lopac
> Priority: Minor
> Fix For: 2.0.0
>
>
> I apologise if this is a known thing, but I have been wondering if anyone can
> give a rationale why do we have two separate operators that perform Google
> Cloud Storage objects copy -- specifically,
> {{gcs_copy_operator.GoogleCloudStorageCopyOperator}} and
> {{gcs_to_gcs.GoogleCloudStorageToGoogleCloudStorageOperator}}. As far as I
> can tell they have nearly the same functionality, with the latter being a bit
> more flexible (with the {{move_object}} flag).
> If both are not needed, I would like to propose removing one of them
> (specifically, the {{gcs_copy_operator}} one); if necessary it can be made
> into a wrapper/subclass of the other one, marked for deprecation.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
