James Grant created OOZIE-2067:
----------------------------------
Summary: Shell Actions should set HADOOP_USER_NAME on unsecured
clusters
Key: OOZIE-2067
URL: https://issues.apache.org/jira/browse/OOZIE-2067
Project: Oozie
Issue Type: Bug
Affects Versions: 4.0.1, 4.0.0
Reporter: James Grant
Priority: Minor
On a secure cluster executing a Hadoop tool within a shell action will mean
that any resulting Hadoop interaction will run as the workflow user. On an
insecure cluster this is not the case since the Hadoop user is lost when
control is passed to the executable or script.
We can work around this by adding
"<env-var>HADOOP_USER_NAME=${wf:user()}</env-var>" to the workflow if deployed
on an insecure cluster.
I propose that we automatically add the HADOOP_USER_NAME environment variable
if UserGroupInformation.isSecurityEnabled() is false. This way more scripts and
workflows will behave in the same way in both secure and insecure clusters.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
