You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Satish Subhashrao Saley (JIRA)" <ji...@apache.org> on 2018/10/12 01:06:00 UTC

[jira] [Moved] (OOZIE-3367) Using && in EL expressions in oozie bundle.xml files generates parse errors

     [ https://issues.apache.org/jira/browse/OOZIE-3367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Satish Subhashrao Saley moved PIG-5364 to OOZIE-3367:
-----------------------------------------------------

        Key: OOZIE-3367  (was: PIG-5364)
    Project: Oozie  (was: Pig)

> Using && in EL expressions in oozie bundle.xml files generates parse errors
> ---------------------------------------------------------------------------
>
>                 Key: OOZIE-3367
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3367
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Satish Subhashrao Saley
>            Assignee: Satish Subhashrao Saley
>            Priority: Major
>
> [~wlauer@yahoo-inc.com]reported -
> I need to put a logical AND into an expression in an oozie bundle (in the enabled flag on the coordinator). When I try "{{A && B}}", oozie gives me a perfectly understandable error about this being invalid XML ({{XML schema error, The entity name must immediately follow the '&' in the entity reference.}}). But when I try to replace this with an XML entity ({{A && B}}), I get an unexpected error that seems to indicate that a space (or something else) is getting injected unexpectedly into my expression:
> {noformat}
> Bundle Job submission Error: [E1004: Expression language evaluation error, Encountered "&", expected one of ["}", ".", ">", "gt", "<", "lt", "==", "eq", "<=", "le", ">=", "ge", "!=", "ne", "[", "+", "-", "*", "/", "div", "%", "mod", "and", "&&", "or", "||", ":", "(", "?"]]
> {noformat}
> Any idea how I can get the expression "A && B" to be parsed correctly in an oozie bundle.xml file?
> It turned out to be a bug in Oozie. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)