[OOZIE-2748] NPE in LauncherMapper.printArgs()

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.2.0
• Fix Version/s: 5.0.0b1, 4.3.1
• Component/s: core
• Assignee: Peter Bacsko
• Reporter: Peter Bacsko
• Created: 30/Nov/16 10:31
• Updated: 25/Jan/18 21:00
• Resolved: 06/Jan/17 18:46

Description

If we define argument for the Spark action like this

        <spark xmlns="uri:oozie:spark-action:0.2">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <configuration>
                <property>
                    <name>oozie.use.system.libpath</name>
                    <value>true</value>
                </property>
                <property>
                    <name></name>
                    <value></value>
                </property>
            </configuration>
            <master>yarn-cluster</master>
            <mode>cluster</mode>
            <name>Something</name>
            <class&gt;package.of.my.Class</class&gt;
            <jar>${nameNode}/myjar.jar</jar>
            <arg></arg>    <---  cause of the NPE
        </spark>

then we get a NullPointerException in LauncherMapper:

Failing Oozie Launcher, Main class [org.apache.oozie.action.hadoop.SparkMain], exception invoking main(), null
java.lang.NullPointerException
	at org.apache.oozie.action.hadoop.LauncherMapper.printArgs(LauncherMapper.java:627)
	at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:212)
	at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
...

Issue Links

• is broken by: OOZIE-2244 Oozie should mask passwords in the logs when logging command arguments
• is duplicated by: OOZIE-2749 Logging command arguments fails in certain scenarios when using EL functions.