[
https://issues.apache.org/jira/browse/NIFI-8344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306432#comment-17306432
]
ASF subversion and git services commented on NIFI-8344:
-------------------------------------------------------
Commit e1b9548ab68ece3a9904f50cd42898e0d41ce166 in nifi's branch
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e1b9548 ]
NIFI-8344: Introduced new Rollover Tail Period property
This closes #4916.
Signed-off-by: Tamas Palfy <[email protected]>
> Allow TailFile to continue tailing a file for some time after it has been
> rolled over
> -------------------------------------------------------------------------------------
>
> Key: NIFI-8344
> URL: https://issues.apache.org/jira/browse/NIFI-8344
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> TailFile makes the assumption that once a file has been rolled over, it will
> never be appended to. If the file's Last Modified timestamp changes, the
> processor assumes that it's a new file and imports the entire contents of the
> file again.
> However, one practice that I've encountered is that users have a syslog
> server that rotates periodically. To rotate, they rename the existing file,
> and then restart the server. When that happens, the server will flush out any
> data that it has buffered to the file that was just rolled over, and then
> begin writing to the new file.
> This results in the TailFile processor ingesting the entire file that has
> been rolled over. Because we can't keep state about every file that is rolled
> over, we should introduce a property that allows the user to indicate that
> upon rollover they want to continue tailing that rolled over file until it is
> no longer being written to, and then begin tailing the new file.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
