airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berislav Lopac (JIRA)" <j...@apache.org>
Subject [jira] [Work started] (AIRFLOW-2326) Duplicate GCS copy operator
Date Tue, 17 Apr 2018 09:07:00 GMT

     [ https://issues.apache.org/jira/browse/AIRFLOW-2326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Work on AIRFLOW-2326 started by Berislav Lopac.
-----------------------------------------------
> 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
>
> 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)

Mime
View raw message