Description
In most of the Oozie actions we can set custom environment variables configured in workflow.xml / job.properties. This works in most of the cases but there is a failure scenario:
job.properties: oozieLauncherEnv=HADOOP_CLIENT_OPTS=-Dfile.encoding=UTF-8 workflow.xml: <property> <name>oozie.launcher.env</name> <value>${oozieLauncherEnv}</value> </property>
With this setup Oozie throws an error:
Caused by: java.lang.IllegalArgumentException: Invalid launcher setting for environment variables: "HADOOP_CLIENT_OPTS=-Dfile.encoding=UTF-8". <env> should contain a list of ENV_VAR_NAME=VALUE separated by the ':' character. Example on Unix: A=foo1:B=foo2
In my opinion Oozie should handle properties' value which contains (multiple) key=value content.