Ovidiu Gheorghioiu created HADOOP-12728:
-------------------------------------------
Summary: "hadoop jar my.jar" should probably prioritize my.jar in
the classpath by default
Key: HADOOP-12728
URL: https://issues.apache.org/jira/browse/HADOOP-12728
Project: Hadoop Common
Issue Type: Improvement
Components: scripts
Affects Versions: 2.7.1
Reporter: Ovidiu Gheorghioiu
Assignee: Allen Wittenauer
Priority: Minor
Found this surprising behavior when testing a dev version of a jar that was
already in the hadoop classpath: "hadoop jar ./my.jar" used the system
my.jar, which was an old version that did not contain my bug fix. Since
"hadoop jar" is the rough equivalent of running an executable, it should use
the version passed on the command line.
Even worse than my case (which took a while to figure out with log messages) is
when I'd be testing that the new version works the same as the old in some use
case. Then I'd think it did, even though the new version was completely broken.
Allen mentioned verbally that there are some tricky aspects to this, but to
open this issue for tracking / brainstorming.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)