Thanks Mona. I was able to get it to work this way, though it is less than ideal.
On Mon, Jul 9, 2012 at 11:08 AM, Mona Chitnis <[email protected]> wrote: > Hello Tim, > > The executable will always be looked for in the application's localized > current working directory(in this case - > /hdata02/hadoop/mapred/local/taskTracker/oozie/jobcache/job_201206011141_71 > 96/attempt_201206011141_7196_m_000000_0/work) > > Hence you should put your executable in your workflow directory. Then use > the <file> tag to refer to it with a symbolic name if required, as shown > here. > > <file>${EXEC}#${EXEC}</file> <!--Copies the executable to compute node's > current working directory --> > > > EXEC refers to your executable's path in hdfs. > -- > Mona Chitnis > > > > > On 7/9/12 2:51 AM, "Tim Chan" <[email protected]> wrote: > >>I'm providing: >> >> <env-var>PATH=/usr/local/nz/bin</env-var> >> >>which is where my executable is located. >> >>I get an error saying: >> >>Cannot run program "nzsql" (in directory >>"/hdata02/hadoop/mapred/local/taskTracker/oozie/jobcache/job_201206011141_ >>7196/attempt_201206011141_7196_m_000000_0/work"): >>java.io.IOException: error=2, No such file or directory >> >>The nzsql executable is located in that path I provided. > -- Tim Chan // [email protected] // 213.784.2523
