[
https://issues.apache.org/jira/browse/HADOOP-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604379#action_12604379
]
Doug Cutting commented on HADOOP-3533:
--------------------------------------
> The problem is that JobTracker and TaskTracker are very wide interfaces.
Wide public interfaces? Really? Stuff needed outside mapred package?
Also, if we reorg the tree so that daemon code is no longer in the same jar as
client code (HADOOP-2884), we'll only publish javadoc for the client code, so
what's public in the daemon code will matter a lot less. Is it worth trying to
fix this now?
> I'd much rather have users use JobClient and access the JobTracker via that
> interface than the JobTracker directly.
+1. But some folks deploy Hadoop daemons in other containers (e.g., as a
servlet, SmartFrog, etc.) so we still want someone to be able to write
something like 'new JobTracker(conf).start()', and not be forced to write such
code in the mapred package.
> The api to JobTracker and TaskTracker have changed incompatibly
> ---------------------------------------------------------------
>
> Key: HADOOP-3533
> URL: https://issues.apache.org/jira/browse/HADOOP-3533
> Project: Hadoop Core
> Issue Type: Bug
> Reporter: Owen O'Malley
> Assignee: Owen O'Malley
> Priority: Blocker
> Fix For: 0.18.0
>
> Attachments: compat.patch
>
>
> The JobTracker and TaskTracker classes are currently both public, and while
> working on HADOOP-3532, I discovered that their API's have been changed
> incompatibly. I believe the best course of action is to make their visibility
> package private.
> Thoughts?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
