[
https://issues.apache.org/jira/browse/OOZIE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807281#comment-13807281
]
Robert Kanter commented on OOZIE-1580:
--------------------------------------
Ah, I missed that its calling {{JavaActionExecutor}}; make sense.
I tried editing the mapreduce example by moving its {{<configuration>}}
properties to a separate xml file and including that with {{<job-xml}}:
{code:xml}
<map-reduce>
<job-tracker>${jobTracker}</job-tracker>
<name-node>${nameNode}</name-node>
<prepare>
<delete
path="${nameNode}/user/${wf:user()}/${examplesRoot}/output-data/${outputDir}"/>
</prepare>
<job-xml>foo.xml</job-xml>
</map-reduce>
{code}
The MR job succeeded, but Oozie had an {{IllegalArgumentException}} somewhere:
{noformat}
$ oozie job -info 0000000-131028144305717-oozie-rkan-W@mr-node
ID : 0000000-131028144305717-oozie-rkan-W@mr-node
------------------------------------------------------------------------------------------------------------------------------------
Console URL :
http://localhost:50030/jobdetails.jsp?jobid=job_201310281439_0001
Error Code : IllegalArgumentException
Error Message : IllegalArgumentException: element cannot be null
External ID : job_201310281439_0001
External Status : SUCCEEDED
Name : mr-node
Retries : 0
Tracker URI : localhost:8021
Type : map-reduce
Started : 2013-10-28 21:44 GMT
Status : ERROR
Ended : -
------------------------------------------------------------------------------------------------------------------------------------
{noformat}
You can see that the "external status" is "SUCCEEDED" (and I checked the MR
job); but the action itself was "ERROR". I looked at the Oozie log, but all I
see in there is this:
{noformat}
2013-10-28 14:44:50,525 WARN ActionEndXCommand:542 - SERVER[rkanter-MBP.local]
USER[rkanter] GROUP[-] TOKEN[] APP[map-reduce-wf]
JOB[0000000-131028144305717-oozie-rkan-W]
ACTION[0000000-131028144305717-oozie-rkan-W@mr-node] Error ending action
[mr-node]. ErrorType [ERROR], ErrorCode [IllegalArgumentException], Message
[IllegalArgumentException: element cannot be null]
{noformat}
Can you take a look?
> EL variables don't get resolved in configurations imported from a <job-xml>
> ---------------------------------------------------------------------------
>
> Key: OOZIE-1580
> URL: https://issues.apache.org/jira/browse/OOZIE-1580
> Project: Oozie
> Issue Type: Improvement
> Reporter: Robert Kanter
> Assignee: Bowen Zhang
> Attachments: oozie-1580.patch
>
>
> If you use <job-xml> to include a file that includes an EL variable, it
> doesn't get resolved.
> For example:
> {code:xml|title=foo.xml|borderStyle=solid}
> <configuration>
> <property>
> <name>some.property</name>
> <value>${someVariable}</value>
> </property>
> </configuration>
> {code}
> {code:title=job.propertiesl|borderStyle=solid}
> ...
> someVariable=bar
> {code}
> Then in the submitted job, {{some.property}} will be equal to
> "{{$\{someVariable}}}" when we would like it to be "{{bar}}".
--
This message was sent by Atlassian JIRA
(v6.1#6144)
