[HADOOP-9488] FileUtil#createJarWithClassPath only substitutes environment variables from current process environment/does not support overriding when launching new process

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.1.0-beta
• Component/s: fs
• Assignee: Chris Nauroth
• Reporter: Chris Nauroth
• Created: 19/Apr/13 16:57
• Updated: 12/May/16 18:26
• Resolved: 19/Apr/13 19:32

Description

FileUtil#createJarWithClassPath always uses System#getEnv for substitution of environment variables in the classpath bundled into the jar manifest. YARN launches container processes with a different set of environment variables, so the method needs to support providing environment variables different from the current process.

Issue Links

• is part of: HADOOP-8562 Enhancements to support Hadoop on Windows Server and Windows Azure environments
• relates to: MAPREDUCE-4987 TestMRJobs#testDistributedCache fails on Windows due to classpath problems and unexpected behavior of symlinks
• relates to: YARN-593 container launch on Windows does not correctly populate classpath with new process's environment variables and localized resources