Hi, When using the Shell Action, and the DefaultContainerExecutor in Yarn, everything you do in your shell script will run as the Yarn user. This is a limitation of the DCE, and there's nothing we can really do about that. If you use the LinuxContainerExecutor, and configure it properly, the Shell Action will run as the correct user.
If you don't want to worry about all that, you can use Oozie's Java API from the Java Action, which doesn't have this user problem. Alternatively, you can use the subworkflow action. - Robert On Sat, Nov 14, 2015 at 10:51 PM, Sabbidi, Prashanth < [email protected]> wrote: > Hi, > > I am trying to submit an oozie job using oozie client api, from another > oozie wf. However, the launched job using api is taking "yarn" as user, and > failing. > Its not taking the parent job user or current logged in user. > > Can someone please advice, how can we ensure the launched job from api > also takes the same user as parent job. > >
