[
https://issues.apache.org/jira/browse/NIFI-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15871872#comment-15871872
]
Andre F de Miranda edited comment on NIFI-3213 at 2/17/17 1:43 PM:
-------------------------------------------------------------------
bq. NIFI-3213: ListFile do not skip obviously old files
bq. Fixed TestListFile.testFilterAge to make it consistent. It used to use the
same last modified timestamp throughout the test that is set at the beginning
of the test. It caused different test results because the meaning of `age1` to
`age5` can vary at the later part of the test, as the test also make use of
Thread.sleep.
bq. This fix reset age variables and last modified timestamp of test input
files before executing next run, to ensure the meaning of age variables to be
consistent.
was (Author: trixpan):
NIFI-3213: ListFile do not skip obviously old files
Fixed TestListFile.testFilterAge to make it consistent.
It used to use the same last modified timestamp throughout the test
that is set at the beginning of the test.
It caused different test results because the meaning of `age1` to `age5`
can vary at the later part of the test, as the test also make use of
Thread.sleep.
This fix reset age variables and last modified timestamp of test input
files before executing next run, to ensure the meaning of age
variables to be consistent.
> 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)
