[
https://issues.apache.org/jira/browse/NIFI-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15376212#comment-15376212
]
ASF GitHub Bot commented on NIFI-1959:
--------------------------------------
Github user JPercivall commented on the issue:
https://github.com/apache/nifi/pull/490
@pvillard31 I think you should be able to leverage the checksum in order to
check if the file that is there is the one that was previously read. Maybe
convert the logic found
[here](https://github.com/apache/nifi/blob/d3d59d58a51ded47ba1b7ebf87a79f678ab41cf2/nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/TailFile.java#L791-L791)
into it's own function and reuse it. This might need to be a configurable
property though (not sure about the performance implications, esp for an
extreme corner case).
> TailFile not ingesting data when tailed file is moved with no rolling pattern
> -----------------------------------------------------------------------------
>
> Key: NIFI-1959
> URL: https://issues.apache.org/jira/browse/NIFI-1959
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Affects Versions: 0.6.1
> Reporter: Pierre Villard
> Assignee: Pierre Villard
> Priority: Minor
> Fix For: 1.0.0
>
>
> In case "Rolling Filename Pattern" is not set by user and if the tailed file
> is moved, then the new file will not be tailed.
> Besides, in such case, the processor will be endlessly triggered without
> ingesting data: it creates a lot of tasks and consumes CPU. The reason is it
> never goes in if statement L448.
> A solution is to look at size() and lastUpdated() of the tailed file to
> detect a "rollover". However it won't allow the processor to ingest the
> potential data added in the tailed file just before being moved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
