Current Situation
From official documentation
- Each time a listing is performed, the files with the latest timestamp will be excluded and picked up during the next execution of the processor. This is done to ensure that we do not miss any files, or produce duplicates, in the cases where files with the same timestamp are written immediately before and after a single execution of the processor.
Improvement Proposal
- If we are calling the ListHDFS only after a certain operation which populates an HDFS directory has finished, it is pointless to skip the last file, and avoiding this behavior is tricky.
- A mandatory property "skip last" should be implemented in order to be able to actively decide whether or not this behavior is necessary, based on the use case.
- This is also particularly useful in combination with
NIFI-6462