[
https://issues.apache.org/jira/browse/APEXMALHAR-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15357592#comment-15357592
]
Sanjay M Pujare commented on APEXMALHAR-2069:
---------------------------------------------
Yes, I noticed that but the actual test that is doing this is
testIdempotencyWithBlocksThreshold()
And testFirstWindowAfterRecovery() just calls this test (which concerns me a
bit).
In any case my observation is that the test behavior is not consistent and even
in isolation I can get it to fail. I think the test (or tests) should be
cleaned up to make them repeatable and consistent.
> FileSplitterInput and TimeBasedDirectoryScanner - move operational fields
> initialization from constructor to setup
> ------------------------------------------------------------------------------------------------------------------
>
> Key: APEXMALHAR-2069
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2069
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Vlad Rozov
>
> For example, there is no need for scanService to be initialized in the
> constructor. It should be done during operator setup().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
