Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <451830954.1213830225059.JavaMail.jira@brutus>
Date: Wed, 18 Jun 2008 16:03:45 -0700 (PDT)
From: "Doug Cutting (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3533) The api to JobTracker and
 TaskTracker have changed incompatibly
In-Reply-To: <1878681991.1213201245134.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-3533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606132#action_12606132 ] 

Doug Cutting commented on HADOOP-3533:
--------------------------------------

You might file a new issue now, while you're thinking about it, to remove all these deprecations.  The patch could be generated by simply reversing this patch.

> 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
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>            Priority: Blocker
>             Fix For: 0.18.0
>
>         Attachments: api-fix.patch, 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.