Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <260067898.1217080051751.JavaMail.jira@brutus>
Date: Sat, 26 Jul 2008 06:47:31 -0700 (PDT)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3801) Change the job state observer
 classes to interfaces
In-Reply-To: <302967229.1216660891610.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-3801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617172#action_12617172 ] 

Steve Loughran commented on HADOOP-3801:
----------------------------------------

As someone who would add a listener to his todo list, can I state that it doesn't make that much difference to me. If it was an abstract class, I'd have to create a non-static inner class to handle the events; if it was an interface, I may still end up doing the same thing, though there it would be more optional.


> Change the job state observer classes to interfaces
> ---------------------------------------------------
>
>                 Key: HADOOP-3801
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3801
>             Project: Hadoop Core
>          Issue Type: Improvement
>            Reporter: Owen O'Malley
>            Assignee: Vivek Ratan
>
> Schedulers will most often want to be the observers of the job state events in a single class. Therefore, I think they should  be interfaces which can have multiple inheritance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.