[
https://issues.apache.org/jira/browse/GOBBLIN-739?focusedWorklogId=228186&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-228186
]
ASF GitHub Bot logged work on GOBBLIN-739:
------------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/19 07:10
Start Date: 16/Apr/19 07:10
Worklog Time Spent: 10m
Work Description: htran1 commented on pull request #2606: [GOBBLIN-739]
Add a way to propagate the Azkaban job config to Gobbli…
URL: https://github.com/apache/incubator-gobblin/pull/2606
…n on YARN
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
- [X] 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-739
### Description
- [X] Here are some details about my PR, including screenshots (if
applicable):
The AzkabanGobblinYarnAppLauncher can be used to launch a Gobblin
application master on YARN, which then loads configuration from an
application.conf file. Currently, the application.conf is pre-generated and
packaged with the Azkaban job zip. This results in duplication of config
between the Azkaban job properties and the application.conf file. It also
doesn't allow user overrides in the Azkaban UI to be propagated to the app
master and containers.
A config (gobblin.yarn.akabanConfigOutputPath) is added to specify an output
path to write the Azkaban job config to in HOCON format. The gobblin yarn
config such as gobblin.yarn.app.master.files.local and
gobblin.yarn.container.files.local can be set to point to the output file.
### Tests
- [X] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [x] 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]
Issue Time Tracking
-------------------
Worklog Id: (was: 228186)
Time Spent: 10m
Remaining Estimate: 0h
> Add a way to propagate the Azkaban job config to Gobblin on YARN
> ----------------------------------------------------------------
>
> Key: GOBBLIN-739
> URL: https://issues.apache.org/jira/browse/GOBBLIN-739
> Project: Apache Gobblin
> Issue Type: Task
> Reporter: Hung Tran
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The AzkabanGobblinYarnAppLauncher can be used to launch a Gobblin application
> master on YARN, which then loads configuration from an application.conf file.
> Currently, the application.conf is pre-generated and packaged with the
> Azkaban job zip. This results in duplication of config between the Azkaban
> job properties and the application.conf file. It also doesn't allow user
> overrides in the Azkaban UI to be propagated to the app master and containers.
> A config should be added to specify an output path to write the Azkaban job
> config to in HOCON format. The gobblin yarn config such as
> gobblin.yarn.app.master.files.local and gobblin.yarn.container.files.local
> can be set to point to the output file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
