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

Mark Payne commented on NIFI-994:
---------------------------------

We should make sure that we also address the following scenarios:

- If the file to tail does not exist, we should generate a WARN message but not 
make the Processor invalid. It will be common to tail the same files on several 
systems and just because a log file, for example, may not yet exist doesn't 
mean the processor should be invalid. Should just warn, yield, and try again 
after the yield period.
- Should have a property that indicates where to start tailing. Valid options 
would be: Beginning of Time (pull in all the rolled over files that you can!), 
Beginning of Tailed File, Now (Do not pull "historical" data). Need to ensure 
that this takes effect only when we begin tailing a new file. I.e., after we 
start tailing a file, we should continue to tail from wherever we left off.

> Processor to tail files
> -----------------------
>
>                 Key: NIFI-994
>                 URL: https://issues.apache.org/jira/browse/NIFI-994
>             Project: Apache NiFi
>          Issue Type: New Feature
>    Affects Versions: 0.4.0
>            Reporter: Joseph Percivall
>            Assignee: Mark Payne
>             Fix For: 0.4.0
>
>         Attachments: 0001-NIFI-994-Initial-import-of-TailFile.patch
>
>
> It's a very common data ingest situation to want to input text into the 
> system by "tailing" a file, most commonly log files. Currently we don't have 
> an easy way to do this. 
> A simple processor to tail a file would benefit many users. There would need 
> to be an option to not just tail a file but pick up where the processor left 
> off if it is interrupted.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to