hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bieniosek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-2024) Make StatusHttpServer (usefully) subclassable
Date Fri, 16 Nov 2007 19:24:43 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-2024?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543176
] 

Michael Bieniosek commented on HADOOP-2024:
-------------------------------------------

See also the StatusHttpServer portion of the webdav_wip2 patch on HADOOP-496 for more things
that can be generalized.  

Also, the constructor should probably not add the TaskGraphServlet.


> Make StatusHttpServer (usefully) subclassable
> ---------------------------------------------
>
>                 Key: HADOOP-2024
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2024
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: stack
>            Priority: Minor
>         Attachments: statushttpserver.patch
>
>
> hbase puts up webapps modelled on those deployed by dfs and mapreduce.  Currently it
does this by copying the bulk of StatusHttpServer down to hbase util as a new class named
InfoServer.  StatusHttpServer is copied rather than subclassed because I need access to the
currently-private resource loading.
> As is, understandably, all webapp-related resources are presumed under the first 'webapps'
directory found.  It doesn't allow for the new condition where some resources can be found
in hadoop and then others in hbase.

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


Mime
View raw message