[ https://issues.apache.org/jira/browse/APEXMALHAR-2103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15308863#comment-15308863 ]
Priyanka Gugale commented on APEXMALHAR-2103: --------------------------------------------- Hi, I think the problem is not with wrong keys in general. Key is wrong only in case where input is absolute file path and not the directory path. When input is a file, we don't set it's directoryPath in metadata and that is causing the problem. I would suggest we should fix it by hadling reference time datastructure for file inputs. Here is the code changes for what I am suggesting: https://github.com/apache/incubator-apex-malhar/compare/master...DT-Priyanka:APEXMALHAR-2103-fix-for-file-input > 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)