Hi, One of the caveats of the shell action is that in a non-secure cluster, it will run scripts as the mapreduce user (i.e. mapred) instead of the user who submitted the job. There is unfortunately nothing we can do about that.
I recommend you take a look at this blog post I wrote about the Shell and Java actions, it contains a lot of useful information about them, including caveats like this one. http://blog.cloudera.com/blog/2013/03/how-to-use-oozie-shell-and-java-actions/ On Thu, Jun 19, 2014 at 10:16 PM, Savitha Devi Inbasekaran < [email protected]> wrote: > I am running a python script in oozie workflow. The python script reads > file from hdfs manipulate and write it back to hdfs in new folder. I am not > getting any error while running the oozie workflow. But manipulated data is > not written in hdfs. I do see that new folder by default has the user a > mapred. I am not much sure whether this is related to mapred user. I am > running the oozie workflow as hdfs user. The python script when ran from > shell script it runs successfully and gives the expected result. > > Any help would be appreciated. > > Thanks! > >
