falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] [Commented] (FALCON-351) Oozie EL extension not used
Date Fri, 14 Mar 2014 10:41:46 GMT

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

Jean-Baptiste Onofré commented on FALCON-351:

Thanks [~shwethags], I forgot this step. The issue is that package.sh didn't work for me.

That's why I did the oozie preparation "by hand".

I'm retesting. Thanks again.

> 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

View raw message