You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Dénes Bodó (Jira)" <ji...@apache.org> on 2022/04/08 13:31:00 UTC
[jira] [Created] (OOZIE-3661) Oozie cannot handle environment variables with key=value content
Dénes Bodó created OOZIE-3661:
---------------------------------
Summary: Oozie cannot handle environment variables with key=value content
Key: OOZIE-3661
URL: https://issues.apache.org/jira/browse/OOZIE-3661
Project: Oozie
Issue Type: Bug
Components: core
Affects Versions: 5.2.1
Reporter: Dénes Bodó
Assignee: Dénes Bodó
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:
{noformat}
job.properties:
oozieLauncherEnv=HADOOP_CLIENT_OPTS=-Dfile.encoding=UTF-8
workflow.xml:
<property>
<name>oozie.launcher.env</name>
<value>${oozieLauncherEnv}</value>
</property>{noformat}
With this setup Oozie throws an error:
{noformat}
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{noformat}
In my opinion Oozie should handle properties' value which contains (multiple) key=value content.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)