[GitHub] [incubator-gobblin] chiragtodarka opened a new pull request #2816: [GOBBLIN-968] Honor file split size for HadoopFileInputSource

[GitBox <gi...@apache.org>]

chiragtodarka opened a new pull request #2816: [GOBBLIN-968] Honor file split size for HadoopFileInputSource
URL: https://github.com/apache/incubator-gobblin/pull/2816
 
 
   Set the value of SPLIT_MAXSIZE and SPLIT_MINSIZE in FileInputFormat
   class from the configs (source.hadoop.file.input.split.minsize and
   source.hadoop.file.input.split.maxsize) passed from .pull file.
   
   Dear Gobblin maintainers,
   
   Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
   
   
   ### JIRA
   - [ ] My PR addresses the following [Gobblin JIRA](https://issues.apache.org/jira/browse/GOBBLIN/) issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"
       - https://issues.apache.org/jira/browse/GOBBLIN-968
   
   
   ### Description
   - [ ] Here are some details about my PR, including screenshots (if applicable): NA
   
   
   ### Tests
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: It is passing configs from .pull to set properties in 'Job' object, no separate unit test case needed. 
   
   
   ### Commits
   - [ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
       1. Subject is separated from body by a blank line
       2. Subject is limited to 50 characters
       3. Subject does not end with a period
       4. Subject uses the imperative mood ("add", not "adding")
       5. Body wraps at 72 characters
       6. Body explains "what" and "why", not "how"
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services