question Re: Nifi: file not picked from input directory after first ime in Support Questions

Nifi: file not picked from input directory after first ime

manishg — Thu, 14 Sep 2023 11:21:18 GMT

I have a nifi flow, working fine. It picks file from a source directory, processes it, and file is deleted from source directory once picked up.

This all works fine first time. But later on, if I copy another file in source directory, that file is not picked up. I even stop all processors, clean any queue if not empty, and restart processors, but still file is not picked from input directory.

What causes this behaviour?

As a result, I have to stop-restart nifi, making it a bit cumbersome.

PS: Based on some google suggestions, I tried to delete flowfile_repository, but it doesn't allow so with message 'Device or resource busy'.

Re: Nifi: file not picked from input directory after first ime

manishg — Thu, 14 Sep 2023 11:41:36 GMT

Got the answer. First processor has listing strategy set to 'Tracking Timestamps', and copied file has older timestamp than the latest tracked one.

Re: Nifi: file not picked from input directory after first ime

gtorres — Thu, 14 Sep 2023 15:17:42 GMT

What processors are you using? List or Get files?

Re: Nifi: file not picked from input directory after first ime

MattWho — Thu, 14 Sep 2023 16:55:32 GMT

@manishg
Copying a file should have resulted in a new timestamp making it newer than the last file you previously listed. However, moving a file typically does not change timestamps on the file. My guess here is you moved a file into the directory instead of copy?

Matt

Re: Nifi: file not picked from input directory after first ime

manishg — Fri, 15 Sep 2023 02:24:47 GMT

I used docker copy command.

Re: Nifi: file not picked from input directory after first ime

manishg — Fri, 15 Sep 2023 02:25:14 GMT

Its ListFile.