You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ephraim E Anierobi (Jira)" <ji...@apache.org> on 2020/03/25 12:36:00 UTC

[jira] [Commented] (AIRFLOW-5611) Add ability to specify a maximum modified time for objects in GoogleCloudStorageToGoogleCloudStorageOperator

    [ https://issues.apache.org/jira/browse/AIRFLOW-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066642#comment-17066642 ] 

Ephraim E Anierobi commented on AIRFLOW-5611:
---------------------------------------------

This issue has been resolved. The pullĀ  request isĀ [https://github.com/apache/airflow/pull/7791]

> Add ability to specify a maximum modified time for objects in GoogleCloudStorageToGoogleCloudStorageOperator
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRFLOW-5611
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-5611
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: gcp
>    Affects Versions: 1.10.5
>            Reporter: Joel Croteau
>            Assignee: Ephraim E Anierobi
>            Priority: Major
>              Labels: gsoc, gsoc2020, mentor
>
> The fact that I can specify a minimum modified time to filter objects on in GoogleCloudStorageToGoogleCloudStorageOperator but not a maximum seems rather arbitrary. Especially considering the typical usage scenario of running a copy on a schedule, I would like to be able to find objects created within a particular schedule interval for my execution, and not just copy all of the latest objects.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)