nifi/nifi-nar-bundles/nifi-extension-utils
Koji Kawamura e68ff153e8
NIFI-3332: ListXXX to not miss files with the latest processed timestamp
Before this fix, it's possible that ListXXX processors can miss files those have the same timestamp as the one which was the latest processed timestamp at the previous cycle. Since it only used timestamps, it was not possible to determine whether a file is already processed or not.

However, storing every single processed identifier as we used to will not perform well.
Instead, this commit makes ListXXX to store only identifiers those have the latest timestamp at a cycle to minimize the amount of state data to store.

NIFI-3332: ListXXX to not miss files with the latest processed timestamp

- Fixed TestAbstractListProcessor to use appropriate time precision.
  Without this fix, arbitrary test can fail if generated timestamp does
  not have the desired time unit value, e.g. generated '10:51:00' where
  second precision is tested.
- Fixed TestFTP.basicFileList to use millisecond time precision explicitly
  because FakeFtpServer's time precision is in minutes.
- Changed junit dependency scope to 'provided' as it is needed by
  ListProcessorTestWatcher which is shared among different modules.

This closes #1975.

Signed-off-by: Bryan Bende <bbende@apache.org>
2017-08-28 11:31:04 -04:00
..
nifi-hadoop-utils NIFI-4311 Allowing umask to get set properly before initializing the FileSystem 2017-08-22 22:40:26 +02:00
nifi-processor-utils NIFI-3332: ListXXX to not miss files with the latest processed timestamp 2017-08-28 11:31:04 -04:00
nifi-record-utils NIFI-4311 Allowing umask to get set properly before initializing the FileSystem 2017-08-22 22:40:26 +02:00
pom.xml NIFI-3997: 2017-06-08 15:22:51 -04:00