You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Bacsko (JIRA)" <ji...@apache.org> on 2017/05/10 12:17:04 UTC
[jira] [Updated] (OOZIE-2872) Address backward compatibility issue
introduced by OOZIE-2748
[ https://issues.apache.org/jira/browse/OOZIE-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko updated OOZIE-2872:
--------------------------------
Attachment: OOZIE-2872-001.patch
> Address backward compatibility issue introduced by OOZIE-2748
> -------------------------------------------------------------
>
> Key: OOZIE-2872
> URL: https://issues.apache.org/jira/browse/OOZIE-2872
> Project: Oozie
> Issue Type: Bug
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Attachments: OOZIE-2872-001.patch
>
>
> OOZIE-2748 introduced a change which eliminates {{null}} arguments in certain actions. For example if the argument list in a Java action contains {{<arg></arg>}} then Oozie used to pass {{null}} in the args[] array to the {{main()}} method.
> After OOZIE-2748, {{null}} elements are removed. However, there are Oozie users who actually rely on this behaviour and now their workflows are broken.
> We should add a property which tells Oozie whether nulls should be inserted or not.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)