hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michel Tourn (JIRA)" <j...@apache.org>
Subject [jira] Created: (HADOOP-505) Patch for external project it.could.webdav
Date Sun, 03 Sep 2006 17:34:24 GMT
Patch for external project it.could.webdav
------------------------------------------

                 Key: HADOOP-505
                 URL: http://issues.apache.org/jira/browse/HADOOP-505
             Project: Hadoop
          Issue Type: Task
          Components: dfs
            Reporter: Michel Tourn


Context: 
http://issues.apache.org/jira/browse/HADOOP-496
http://could.it/main/a-simple-approach-to-webdav.html

This patch applies to an external project that Hadoop would use as a library.
You can obtain the baseline code:
svn co --revision {"1 Sep 2006 00:00:00 GMT"} http://could.it/repo/webdav/head/
Then apply the attached patch.

Patch details below.
---------------------
Changes in the patch are:

Filehandle leaks prevented it from working on Windows. (in.close() in 3 places)
Filehandle leaks would eventually crash server on Linux.

Now it passes the litmus compliance tests, in both original and HDFS mode.
Mostly had to refine the HTTP status codes.

Decoupled COPY and MOVE
This allows an implementation of MOVE other than COPY-and-delete

There is no new "abstraction code" to support a distributed filesystem backend.
Only: one change to make a java.io.File reference work when it represents a 
non-Windows path on Windows: (unixAbsolute = rootPath.startsWith("/"))


The factory code via servlet properties was extended to allow loading by name:
repositoryClass="it.could.webdav.DAVRepository"
repositoryClass="it.could.webdav.XMLRepository"
repositoryClass="org.apache.hadoop.dfs.webdav.HDFSRepository"

4 classes are subclassed for the alternative implementation:
A few private fields were made protected.
Some constructor logic moved to protected init() method-s so it can be overriden.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message