[
https://issues.apache.org/jira/browse/OOZIE-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13222664#comment-13222664
]
Alejandro Abdelnur commented on OOZIE-736:
------------------------------------------
A solution would be to add to the HadoopAccessorService a new configuration
property
hadoop.configurations= [<AUTHORITY>=<CONFIG_FILE>]*
Where <AUTHORITY> is the HOST:PORT of the Hadoop JT/NN and <CONFIG_FILE> is the
Hadoop configuration file to load from the local filesystem with the defaults
for the corresponding JT/NN.
In addition, a '*' wildcard would be support for the <AUTHORITY>, this would be
used as default if the job used authority does not have a custom config.
The Hadoop configuration file would be looked in the Oozie conf/ directory
An example of this configuration would be:
hadoop.configuration= *=hadoop-defaultconf.xml
myjobtracker:8021=hadoop-cluster1.xml, mynamenode:8020=hadoop-cluster1.xml
> Add support for configurations per JT/NN
> ----------------------------------------
>
> Key: OOZIE-736
> URL: https://issues.apache.org/jira/browse/OOZIE-736
> Project: Oozie
> Issue Type: New Feature
> Components: core
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Assignee: Alejandro Abdelnur
> Priority: Critical
> Fix For: 3.2.0
>
>
> Currently Oozie does not support oozie-server-side configs for the JT/NN and
> users must add all values explicitly in their workflows.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
