apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From deepak-narkhede <...@git.apache.org>
Subject [GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...
Date Wed, 26 Oct 2016 08:35:43 GMT
GitHub user deepak-narkhede reopened a pull request:


    APEXMALHAR-2314 Improper functioning in partitioning for sequentialFileRead for FSRecord

    Fix the StreamCodec for FSRecordReader, initially it was hashcode of blockId's mostly
always unique.
    Hence unable to satisfy the sequentialFileRead property. Now the StreamCodec is modified
to work
    with hashcode of filePath. So all blocks related to a file would be partitioned on same
    Tested with recordReader and verified for sequentialFileRead that all blocks related to
a file are partitioned to single operator.

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

    $ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2314

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 #468
commit 259cc5b80635207e8b0a4d7c0c9b5bc735021de2
Author: deepak-narkhede <mailtodeepakn@gmail.com>
Date:   2016-10-24T11:39:24Z

    APEXMALHAR-2314 Improper functioning in partitioning of sequentialFileRead property of
    Modified the StreamCodec to work with hashcode of filepath rather than blockId.


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message