Berislav Lopac created AIRFLOW-2326:

             Summary: Duplicate GCS copy operator
                 Key: AIRFLOW-2326
             Project: Apache Airflow
          Issue Type: Improvement
            Reporter: Berislav Lopac

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

Reply via email to