ASF GitHub Bot commented on NIFI-3213:

Github user trixpan commented on the issue:

    @ijokarumawak my bad. I was just running a extra set of compilations and I 
noticed that under certain conditions there seems to be a race condition 
    Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 5.66 sec 
<<< FAILURE! - in org.apache.nifi.processors.standard.TestListFile
    testFilterAge(org.apache.nifi.processors.standard.TestListFile)  Time 
elapsed: 1.212 sec  <<< FAILURE!
    org.junit.ComparisonFailure: expected:<age[2].txt> but was:<age[1].txt>
        at org.junit.Assert.assertEquals(Assert.java:115)
        at org.junit.Assert.assertEquals(Assert.java:144)
    Do you want to have a look at it?

> ListFile always skips files with the latest timestamp in an iteration even if 
> the files have existed a while ago
> ----------------------------------------------------------------------------------------------------------------
>                 Key: NIFI-3213
>                 URL: https://issues.apache.org/jira/browse/NIFI-3213
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.0.0, 0.5.0, 0.6.0, 0.5.1, 0.7.0, 0.6.1, 1.1.0, 0.7.1
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
> NIFI-1484 add few lines of code to avoid files to be emitted if those have 
> the latest timestamp within an iteration of listing, because it may still be 
> written at the same time.
> While it doesn't affect much if ListFiles processor is scheduled with a short 
> period of time, such as few ms, but it does affect negatively if an user 
> scheduled it with longer run schedule such as "1 day" or with cron scheduler. 
> For example, user would expect to process list of files per daily basis. Even 
> if a file is saved few hours ago, the processor will skip this, because the 
> file has the latest timestamp within the iteration.

This message was sent by Atlassian JIRA

Reply via email to