You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joe Witt (Jira)" <ji...@apache.org> on 2021/01/27 05:46:01 UTC
[jira] [Resolved] (NIFI-7263) Add a No tracking Strategy to
ListFile/ListFTP
[ https://issues.apache.org/jira/browse/NIFI-7263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Witt resolved NIFI-7263.
----------------------------
Resolution: Fixed
> Add a No tracking Strategy to ListFile/ListFTP
> ----------------------------------------------
>
> Key: NIFI-7263
> URL: https://issues.apache.org/jira/browse/NIFI-7263
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Jens M Kofoed
> Assignee: Waleed Al Aibani
> Priority: Major
> Labels: ListFile, listftp
> Fix For: 1.13.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> The Listfile/ListFTP has 2 Listing Strategies: Tracking Timestamps and Tracking Entities.
> It would be very very nice if the List process also could have a No Tracking (fix it your self) strategy
> If running NIFI in a cluster the List/Fetch is the perfect solution instead of using a GetFile. But we have had many caces where files in the pickup folder has old timestamps, so here we have to use Tracking Entities.
> The issue is in cases where you are not allowed to delete files but you have to make a change to the file filter. The tracking entities start all over, and list all files again.
> In other situations we need to resent all data, and would like to clear the state of the Tracking Entities. But you can't.
> So I have to make a small flow for detecting duplicates. And in some cases just ignore duplicates and in other caces open up for sending duplicates. But it is a pain in the ... to use the Tracking Entities.
> So a NO STRATEGY would be very very nice
--
This message was sent by Atlassian Jira
(v8.3.4#803005)