[
https://issues.apache.org/jira/browse/OOZIE-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416589#comment-13416589
]
Virag Kothari commented on OOZIE-878:
-------------------------------------
bq. I was referring to Kerberos Name Rules as in auth_to_local in core-site.xml
that ought to be present for delegation token renewal.
I understand now, but hadoop's config (core-site.xml) will have many properties
not required in Oozie-client. IMO, it is better to have a separate Oozie client
config even if one of the properties (auth_to_local) is redundant.
bq. Oozie is meant to talk to only one hadoop cluster
I think from 3.2, you can have different hadoop conf dir corresponding to the
NN/JT. Have a look at
'oozie.service.HadoopAccessorService.hadoop.configurations' in oozie-site.xml.
However, I understand if there is a 'default' hadoop cluster for Oozie which
usually is the case, Oozie should pick the JT/NN configurations from the hadoop
config.
> Add oozie-client-site.xml configuration file
> --------------------------------------------
>
> Key: OOZIE-878
> URL: https://issues.apache.org/jira/browse/OOZIE-878
> Project: Oozie
> Issue Type: Improvement
> Components: client
> Affects Versions: 3.2.0
> Reporter: Alejandro Abdelnur
> Fix For: trunk
>
>
> the number of settings on the client side is growing and we cannot get away
> (cleanly) with the current mechanism (EVNs or modifying the oozie script).
> We should introduce a conf/oozie-client-site.xml file where we can do such
> settings.
> For example: OOZIE_URL, authenticator class, if the authentication cookie
> should be saved to file, etc.
> This will also help for defining the KerberosName rules for the client side
> whe HADOOP-8518 goes in.
--
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
