[
https://issues.apache.org/jira/browse/APEXMALHAR-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15303640#comment-15303640
]
ASF GitHub Bot commented on APEXMALHAR-2103:
--------------------------------------------
GitHub user chaithu14 opened a pull request:
https://github.com/apache/incubator-apex-malhar/pull/299
APEXMALHAR-2103 Fixed the scanner issue in FileSplitterInput Class
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/chaithu14/incubator-apex-malhar
APEXMALHAR-2103-ScannerIssue
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-apex-malhar/pull/299.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #299
----
commit 94d01fd5a264684f6b372600a92c1c7d20b12537
Author: Chaitanya <chaita...@datatorrent.com>
Date: 2016-05-27T06:40:48Z
APEXMALHAR-2103 Fixed the scanner issue in FileSplitterInput Class
----
> scanner issues in FileSplitterInput class
> -----------------------------------------
>
> Key: APEXMALHAR-2103
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2103
> Project: Apache Apex Malhar
> Issue Type: Bug
> Reporter: Chaitanya
> Assignee: Chaitanya
>
> Issue: FileSplitter continuously emitting filemetadata even though there is
> a single file.
> Observation: For the same file, While updating and accessing the
> referenceTimes map in FIleSplitterInput and TimeBasedScanner, the Keys are
> different. Because of this, the oldestTimeModification is always null in
> TimeBasedScanner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
