[
https://issues.apache.org/jira/browse/OOZIE-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter resolved OOZIE-1955.
----------------------------------
Resolution: Won't Fix
Unfortunately, one of the caveats of the shell action is that in a
non-Kerberized cluster, it runs as the MapReduce user (i.e. mapred) instead of
the actual user; in a Kerberized cluster, it runs as the actual user. This is
a behavior of Hadoop and there isn't anything we can really do about it.
If all you're doing is running the {{hive -f}} command, you should just use the
Hive action, which does the same thing but as the correct user and includes
some other useful behaviors as well.
> Unable to run hive scripts from Oozie shell action
> ---------------------------------------------------
>
> Key: OOZIE-1955
> URL: https://issues.apache.org/jira/browse/OOZIE-1955
> Project: Oozie
> Issue Type: Bug
> Affects Versions: 4.0.0
> Environment: Hive .12,Oozie 4.0
> Reporter: Anuroopa George
> Fix For: 4.0.0
>
>
> While trying to execute Hive script from shell script(shell action of Oozie)
> using hive -f command,Hive script fails.
> The problem is that the shell script is submitted from Oozie as mapred
> user,and the staging area is created with respect to the user who submits the
> Oozie workflow.So mapred user is unable to
> access this staging area and the hive scripts get failed.
> Below is the exception:
> java.io.IOException: The ownership on the staging directory
> hdfs://nameservice1/user/user1/.staging is not as expected.
> It is owned by user1. The directory must be owned by the submitter mapred or
> by mapred
> at
> org.apache.hadoop.mapreduce.JobSubmissionFiles.getStagingDir(JobSubmissionFiles.java:113)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
