[
https://issues.apache.org/jira/browse/NIFI-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871053#comment-15871053
]
ASF GitHub Bot commented on NIFI-3213:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1335
@trixpan Since the failing test has more Thread.sleep calls than before,
the meaning of variables such as `age1` or `age2` became fragile at the later
part of the test. I added another commit to fix the test case. Also, rebased it
with the latest master just in case.
Thanks again for caching this test issue. Please review the test again, and
let me know if you want me to squash commits.
> 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
(v6.3.15#6346)
