Hello Roman, It seems the resolution of last modified timestamp depends on the file system implementation. https://stackoverflow.com/questions/3805201/how-to-get-ubuntu-file-timestamp-in-millisecond
I reproduced the same behavior on OS X, which uses HFS that has the same limitation of resolution in seconds. https://stackoverflow.com/questions/18403588/how-to-return-millisecond-information-for-file-access-on-mac-os-x-in-java Which file system are you using on your Ubuntu? If it is ext3, then changing it to ext4 may address the issue. Thanks, Koji On Thu, Jun 1, 2017 at 1:25 AM, Roman <[email protected]> wrote: > Hi there, i need help. > > We prepare high load project and tested this processors. All time see > listing.timestamp and processed.timestamp keys without milliseconds > (xxxxxxxxxx000). In this way, if generate several files in one second, not > all files will be listened. > > > Test: > 1. start processor ListFile/ListSFTP > 2. generate 10000 zero size files. my command: for i in {1..10000}; do > touch ./test_$i; done > 3. see processor stats: out 3952 (0 bytes) > > > I'm somewhere wrong? Or is it a bug nifi/java/etc? > > Environment > > Ubuntu 14.04.5 LTS, x64, ext4 file system > Java HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode) > Nifi 1.2.0 From 3a605af, Tagged nifi-1.2.0-RC2 > > > Thanks > Roman > > > > -- > View this message in context: > http://apache-nifi-developer-list.39713.n7.nabble.com/processors-ListFile-ListSFTP-do-not-store-milliseconds-in-timestamp-tp16037.html > Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
