[
https://issues.apache.org/jira/browse/HADOOP-2516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555805#action_12555805
]
Owen O'Malley commented on HADOOP-2516:
---------------------------------------
There isn't a way to get the old functionality without leaving the static
variable. I think the static variable and the usage of it was causing trouble
because the reference was visible before the object was finished being
constructed.
I'm also confused how user code is calling this meaningfully, since it would
have to be running in the job tracker's process, which doesn't load user code.
> HADOOP-1819 removed a public api JobTracker.getTracker in 0.15.0
> ----------------------------------------------------------------
>
> Key: HADOOP-2516
> URL: https://issues.apache.org/jira/browse/HADOOP-2516
> Project: Hadoop
> Issue Type: Bug
> Affects Versions: 0.15.1
> Reporter: Arun C Murthy
> Assignee: Arun C Murthy
> Fix For: 0.16.0
>
>
> HADOOP-1819 removed a 0.14.0 public api {{JobTracker.getTracker}} in 0.15.0.
> http://svn.apache.org/viewvc?view=rev&revision=575438 and
> http://svn.apache.org/viewvc/lucene/hadoop/branches/branch-0.15/src/java/org/apache/hadoop/mapred/JobTracker.java?r1=573708&r2=575438&diff_format=h
> There is a simple work-around i.e. use the return value of
> {{JobTracker.startTracker}} ... yet, is this a 0.15.2 blocker?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
