You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2008/11/04 02:15:44 UTC

[jira] Resolved: (HADOOP-2024) Make StatusHttpServer (usefully) subclassable

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

Tsz Wo (Nicholas), SZE resolved HADOOP-2024.
--------------------------------------------

    Resolution: Duplicate

This issue was fixed as a part of HADOOP-3824.

> Make StatusHttpServer (usefully) subclassable
> ---------------------------------------------
>
>                 Key: HADOOP-2024
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2024
>             Project: Hadoop Core
>          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.