[FALCON-351] Oozie EL extension not used

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: 0.5
• Component/s: oozie
• Assignee: Jean-Baptiste Onofré
• Reporter: Jean-Baptiste Onofré
• Created: 12/Mar/14 12:13
• Updated: 31/Mar/14 13:54
• Resolved: 31/Mar/14 13:54

Description

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:

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)
...

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.

Issue Links

• is related to: FALCON-361 packages.sh output messages are not correct
• is related to: FALCON-362 package.sh should provide a complete and ready to use oozie distribution