[
https://issues.apache.org/jira/browse/NIFI-11891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751942#comment-17751942
]
Pierre Villard commented on NIFI-11891:
---------------------------------------
You can wait for the next release of NiFi that will contain this change and
upgrade your cluster to that version. You could also upgrade to 1.23 now and
build a custom NAR with the changes that were merged.
> Add No Tracking Strategy to ListGCS
> -----------------------------------
>
> Key: NIFI-11891
> URL: https://issues.apache.org/jira/browse/NIFI-11891
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Noura Ali
> Assignee: Pierre Villard
> Priority: Major
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently, when ListGCS runs for the first time, it lists all the available
> files in the specified bucket directory, and when it runs in the next times,
> it lists the files created/modified since last run, using the state stored in
> the processor.
> What is required is that every time the processor runs(runs after first one),
> to list all existing files in GCS specified directory, not the files
> created/modified since last run.
> As I understand this is called "No Tracking" listing strategy that is
> available in most List* processors, but it doesn't exist in ListGCSBucket.
>
> Without this capability, I had to build a whole extra pipeline to stop the
> processor–> clear the state -->start processor, before the ListGCS runs,
> which is prone to issues with extra work and maintenance effort.
>
> Appreciate your help and support.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
