[
https://issues.apache.org/jira/browse/OOZIE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13807112#comment-13807112
]
Bowen Zhang commented on OOZIE-1580:
------------------------------------
FsActionExecutor does call the method parseJobXmlAndConfiguration from
doOperations(). And all the other subclasses of actionExecutor don't invoke any
checks for "job-xml" tab because (i guess) it won't make sense to do it. This
is either by feature design or an existing bug in the code base which in either
case should be outside the scope of this ticket.
> 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)
