[
https://issues.apache.org/jira/browse/OOZIE-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13806988#comment-13806988
]
Robert Kanter commented on OOZIE-1580:
--------------------------------------
The changes will only affect actions that subclass the {{JavaActionExecutor}};
but some action executors, such as the {{FsActionExecutor}} do not so they
won't resolve the variables in their <job-xml> if they have one. I think we
should add a function to {{ActionExecutor}} that can resolve the <job-xml>
variables and then any subclasses (i.e. {{JavaActionExecutor}},
{{FsActionExecutor}}), can simply call it.
> 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)
