autumnust opened a new pull request #2873: [GOBBLIN-1031]Gobblin-on-Yarn locally running Azkaban job skeleton URL: https://github.com/apache/incubator-gobblin/pull/2873 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 - [ ] https://issues.apache.org/jira/browse/GOBBLIN-1031 ### Description - [ ] Here are some details about my PR, including screenshots (if applicable): - The major part of this PR is `AzkabanJobRunner.java` which could power gobblin job to be running using the same Azkaban setting that Linkedin is using internally for job-scheduling, locally. - On top of that, is an Embedded Gobblin JobLauncher that starts a Gobblin-Streaming job and submit ApplictionMaster to `MiniYARNCluster` spun up in the same process. - Also provide a skeleton of configurations that can be used for running the whole job locally. The skeleton has many class-definition that have not been open-sourced or only serve Linkedin-specific purpose, the general-purpose job configuration is still under development. ### Tests - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason: ### 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: [email protected] With regards, Apache Git Services
