You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by deepak-narkhede <gi...@git.apache.org> on 2016/10/24 08:43:11 UTC

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

GitHub user deepak-narkhede opened a pull request:

    https://github.com/apache/apex-malhar/pull/468

    APEXMALHAR-2314 Improper functioning in partitioning for sequencialFileRead for FSRecord

    Fix the StreamCodec for FSRecordReader, initially it was hashcode of blockId's mostly always unique.
    Hence unable to satisfy the sequencialFileRead property. Now the StreamCodec is modified to work
    with hashcode of filePath. So all blocks related to a file would be partitioned on same operator.
    
    Tested with recordReader and verified for sequencialFileRead 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:

    https://github.com/apache/apex-malhar/pull/468.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 #468
    
----
commit fe81d79d2b5ec845b97a93a5cd21514eff5f29fa
Author: deepak-narkhede <ma...@gmail.com>
Date:   2016-10-24T08:23:57Z

    APEXMALHAR-2314 Improper functioning in partitioning of sequencialFileRead property of FSRecordReaderModule.
    
    Fix the StreamCodec for FSRecordReader, initially it was hashcode of blockId's mostly always unique.
    Hence unable to satisfy the sequencialFileRead property. Now the StreamCodec is modified to work
    with hashcode of filePath. So all blocks related to a file would be partitioned on same operator.

----


---
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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by deepak-narkhede <gi...@git.apache.org>.
Github user deepak-narkhede closed the pull request at:

    https://github.com/apache/apex-malhar/pull/468


---
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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by deepak-narkhede <gi...@git.apache.org>.
GitHub user deepak-narkhede reopened a pull request:

    https://github.com/apache/apex-malhar/pull/468

    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 operator.
    
    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:

    https://github.com/apache/apex-malhar/pull/468.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 #468
    
----
commit 259cc5b80635207e8b0a4d7c0c9b5bc735021de2
Author: deepak-narkhede <ma...@gmail.com>
Date:   2016-10-24T11:39:24Z

    APEXMALHAR-2314 Improper functioning in partitioning of sequentialFileRead property of FSRecordReaderModule.
    
    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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by deepak-narkhede <gi...@git.apache.org>.
GitHub user deepak-narkhede reopened a pull request:

    https://github.com/apache/apex-malhar/pull/468

    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 operator.
    
    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:

    https://github.com/apache/apex-malhar/pull/468.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 #468
    
----
commit 259cc5b80635207e8b0a4d7c0c9b5bc735021de2
Author: deepak-narkhede <ma...@gmail.com>
Date:   2016-10-24T11:39:24Z

    APEXMALHAR-2314 Improper functioning in partitioning of sequentialFileRead property of FSRecordReaderModule.
    
    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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by deepak-narkhede <gi...@git.apache.org>.
GitHub user deepak-narkhede reopened a pull request:

    https://github.com/apache/apex-malhar/pull/468

    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 operator.
    
    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:

    https://github.com/apache/apex-malhar/pull/468.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 #468
    
----
commit 3f973043f5d343bcf7cb067269377e4e08c76aff
Author: deepak-narkhede <ma...@gmail.com>
Date:   2016-11-07T09:44:47Z

    APEXMALHAR-2314 Improper functioning in partitioning of sequentialFileRead property of FSRecordReaderModule.
    
    Modified the StreamCodec to work with hashcode of filepath rather than blockId.
    
    Conflicts:
    	library/src/main/java/org/apache/apex/malhar/lib/fs/FSRecordReaderModule.java

----


---
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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by deepak-narkhede <gi...@git.apache.org>.
Github user deepak-narkhede closed the pull request at:

    https://github.com/apache/apex-malhar/pull/468


---
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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by deepak-narkhede <gi...@git.apache.org>.
Github user deepak-narkhede closed the pull request at:

    https://github.com/apache/apex-malhar/pull/468


---
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.
---

[GitHub] apex-malhar pull request #468: APEXMALHAR-2314 Improper functioning in parti...

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/apex-malhar/pull/468


---
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.
---