[ 
https://issues.apache.org/jira/browse/HADOOP-3824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

stack updated HADOOP-3824:
--------------------------

    Attachment: 3824_20080724-v2.patch

Would you consider using this version of your patch?

Only change is to the HttpServer constructor calling out to a new method named 
addWebapps.  Its in this method that we add webapps and servlets rather than up 
in the constructor.  Makes it so a subclass can influence whats loaded (not 
load some or load with different names, etc.).

Use case is something like hbase.  Currently we have a duplicate of the old 
StatusHttpServer.  We call it InfoServer down in hbase-land.  Hbase has webapps 
like those in hadoop-core only they want just some of the webapps+servlets that 
hadoop-core used put up in InfoServer.  We made the duplicate because we 
couldn't subclass old StatusHttpServer (HADOOP-2024 was attempt at getting in a 
patch that would make it subclassable).

Thanks for your consideration.  THanks.

> Refactor org.apache.hadoop.mapred.StatusHttpServer
> --------------------------------------------------
>
>                 Key: HADOOP-3824
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3824
>             Project: Hadoop Core
>          Issue Type: Sub-task
>          Components: dfs, mapred
>            Reporter: Tsz Wo (Nicholas), SZE
>         Attachments: 3824_20080724-v2.patch, 3824_20080724.patch
>
>
> StatusHttpServer is defined in the mapred package but it is used by hdfs 
> classes DataNode, FSNamesystem, SecondaryNameNode.

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

Reply via email to