You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Shwetha G S (JIRA)" <ji...@apache.org> on 2014/03/14 07:20:52 UTC

[jira] [Commented] (FALCON-351) Oozie EL extension not used

    [ https://issues.apache.org/jira/browse/FALCON-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13934674#comment-13934674 ] 

Shwetha G S commented on FALCON-351:
------------------------------------

Need changes in oozie-site.xml to add the mapping of EL function to java function. src/bin/package.sh prepares oozie with config and jar required for EL extensions

> Oozie EL extension not used
> ---------------------------
>
>                 Key: FALCON-351
>                 URL: https://issues.apache.org/jira/browse/FALCON-351
>             Project: Falcon
>          Issue Type: Bug
>          Components: oozie
>    Affects Versions: 0.5
>            Reporter: Jean-Baptiste Onofré
>            Assignee: Jean-Baptiste Onofré
>
> Even adding the falcon-oozie-el-extension*.jar file in oozie/libext folder (and update the war using bin/oozie-setup prepare-war and sharedlibs), when I schedule a process containing EL like now(0,-5), the Oozie bundle job fails:
> {code}
> org.apache.oozie.coord.CoordinatorJobException: E1004: Expression language evaluation error, Unable to evaluate :${now(0,-5)}:
> 	at org.apache.oozie.command.coord.CoordSubmitXCommand.resolveTagContents(CoordSubmitXCommand.java:889)
> 	at org.apache.oozie.command.coord.CoordSubmitXCommand.resolveIOEvents(CoordSubmitXCommand.java:786)
> 	at org.apache.oozie.command.coord.CoordSubmitXCommand.resolveInitial(CoordSubmitXCommand.java:714)
> 	at org.apache.oozie.command.coord.CoordSubmitXCommand.basicResolveAndIncludeDS(CoordSubmitXCommand.java:551)
> 	at org.apache.oozie.command.coord.CoordSubmitXCommand.submit(CoordSubmitXCommand.java:219)
> ...
> {code}
> It looks like the Falcon Oozie EL extension is not loaded by Oozie.
> Maybe it's just an environment/installation issue on my platform, but at least, we have to document it.



--
This message was sent by Atlassian JIRA
(v6.2#6252)