[GitHub] apex-malhar pull request #457: APEXMALHAR-2302 Exposing few properties of FS...
Github user asfgit closed the pull request at: https://github.com/apache/apex-malhar/pull/457 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] apex-malhar pull request #457: APEXMALHAR-2302 Exposing few properties of FS...
Github user deepak-narkhede closed the pull request at: https://github.com/apache/apex-malhar/pull/457 --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] apex-malhar pull request #457: APEXMALHAR-2302 Exposing few properties of FS...
GitHub user deepak-narkhede reopened a pull request: https://github.com/apache/apex-malhar/pull/457 APEXMALHAR-2302 Exposing few properties of FSSplitter and BlockReader operators to FSRecordReaderModule This change includes: 1) Expose blockSize property of FileSplitter operator. 2) Expose minReaders and maxReaders for dynamic partitioning of Block Reader operator. 3) Deprecate readersCount from FSRecordReaderModule. Tested with recordReader application. You can merge this pull request into a Git repository by running: $ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2302 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/457.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 #457 commit 03e59343fa69b71519f7933b70009994420c6ac0 Author: deepak-narkhede Date: 2016-10-21T12:27:01Z APEXMALHAR-2302 Exposing the few properties of FSSplitter and BlockReader operators to FSRecordReaderModule to tune Application. 1) Expose blockSize property of FileSplitter operator. 2) Expose minReaders and maxReaders for dynamic partitioning of Block Reader operator. 3) Deprecate readersCount from FSRecordReaderModule. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] apex-malhar pull request #457: APEXMALHAR-2302 Exposing few properties of FS...
GitHub user deepak-narkhede reopened a pull request: https://github.com/apache/apex-malhar/pull/457 APEXMALHAR-2302 Exposing few properties of FSSplitter and BlockReader operators to FSRecordReaderModule This change adds blockSize property from FileSplitter to FSRecordReaderModule. Tested with RecordReader Application. You can merge this pull request into a Git repository by running: $ git pull https://github.com/deepak-narkhede/apex-malhar APEXMALHAR-2302 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/apex-malhar/pull/457.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 #457 commit 7d07dd32c95546a6c4570453163f9ff47b8a7893 Author: deepak-narkhede Date: 2016-10-21T12:27:01Z APEXMALHAR-2302 Exposing the few properties of FSSplitter and BlockReader operators to FSRecordReaderModule to tune Application. This change includes: 1) Expose blockSize property of FileSplitter operator. 2) Expose minReaders and maxReaders for dynamic partitioning of Block Reader operator. 3) Deprecate readersCount from FSRecordReaderModule. --- 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 infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
