apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APEXMALHAR-2272) sequencialFileRead property on FSInputModule not functioning as expected
Date Mon, 03 Oct 2016 07:16:20 GMT

    [ https://issues.apache.org/jira/browse/APEXMALHAR-2272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15541741#comment-15541741

ASF GitHub Bot commented on APEXMALHAR-2272:

GitHub user yogidevendra opened a pull request:


    APEXMALHAR-2272 : Fixed sequentialFileRead on FSInputModule


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yogidevendra/apex-malhar APEXMALHAR-2272-sequencialFileRead

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #439
commit f01b56b5a671572f37e487f422db99994cbe5537
Author: yogidevendra <yogidevendra@apache.org>
Date:   2016-10-01T02:49:56Z

    APEXMALHAR-2272 : Fixed sequencialFileRead on FSInputModule


> sequencialFileRead property on FSInputModule not functioning as expected
> ------------------------------------------------------------------------
>                 Key: APEXMALHAR-2272
>                 URL: https://issues.apache.org/jira/browse/APEXMALHAR-2272
>             Project: Apache Apex Malhar
>          Issue Type: Bug
>            Reporter: Yogi Devendra
>            Assignee: Yogi Devendra
>            Priority: Minor
> When there is single large file in the input directory, and we have multiple partitions
for BlockReader and sequencialFileRead is set to true.
> Only one BlockReader instance should be active; other BlockReader instances should remain
> This is because sequencialFileRead makes sure that blocks of the file are read serially
by same BlockReader instance. 
> Observed behavior is all BlockReader instances are reading data which means sequencialFileRead
property is not functioning as expected.

This message was sent by Atlassian JIRA

View raw message