[
https://issues.apache.org/jira/browse/HADOOP-6097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756899#action_12756899
]
Mahadev konar commented on HADOOP-6097:
---------------------------------------
ant test passes with this patch except for TestHdfsProxy in contrib which fails
due to the following unrelated reason:
{code}
Testcase: testHdfsProxyInterface took 6.078 sec
Caused an ERROR
org/apache/commons/cli/ParseException
java.lang.NoClassDefFoundError: org/apache/commons/cli/ParseException
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:59)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:79)
at
org.apache.hadoop.hdfsproxy.TestHdfsProxy.testHdfsProxyInterface(TestHdfsProxy.java:222)
{code}
> Multiple bugs w/ Hadoop archives
> --------------------------------
>
> Key: HADOOP-6097
> URL: https://issues.apache.org/jira/browse/HADOOP-6097
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.18.0, 0.18.1, 0.18.2, 0.18.3, 0.19.0, 0.19.1, 0.19.2,
> 0.20.0, 0.20.1
> Reporter: Ben Slusky
> Assignee: Ben Slusky
> Fix For: 0.20.2
>
> Attachments: HADOOP-6097-v2.patch, HADOOP-6097.patch
>
>
> Found and fixed several bugs involving Hadoop archives:
> - In makeQualified(), the sloppy conversion from Path to URI and back mangles
> the path if it contains an escape-worthy character.
> - It's possible that fileStatusInIndex() may have to read more than one
> segment of the index. The LineReader and count of bytes read need to be reset
> for each block.
> - har:// connections cannot be indexed by (scheme, authority, username) --
> the path is significant as well. Caching them in this way limits a hadoop
> client to opening one archive per filesystem. It seems to be safe not to
> cache them, since they wrap another connection that does the actual
> networking.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
