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] Resolved: (HADOOP-2218) Generalize StatusHttpServer so webdav server can use it
Date Fri, 16 Nov 2007 19:22:43 GMT

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

Michael Bieniosek resolved HADOOP-2218.

    Resolution: Won't Fix

Actually, now that I look at it, it's easier just to rewrite the webdav code so it doesn't
use StatusHttpServer and calls the jetty api directly.

I think a better fix would be to rewrite StatusHttpServer so that it uses a JettyWrapper superclass,
and doesn't contain any mapreduce-specific code.  

> Generalize StatusHttpServer so webdav server can use it
> -------------------------------------------------------
>                 Key: HADOOP-2218
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2218
>             Project: Hadoop
>          Issue Type: New Feature
>          Components: fs
>    Affects Versions: 0.15.0
>            Reporter: Michael Bieniosek
> I'd like to make HADOOP-496 stand alone, so that I can make a hadoop-webdav jar that
works against stock hadoop.  The latest HADOOP-496 patch has only a small patch against StatusHttpServer,
which generalizes it a little bit to make some private methods protected and changes HttpServlet
to Servlet -- the rest is new files.  I'd like to get the part against StatusHttpServer committed.

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

View raw message