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

zhiyong zhang updated HDFS-472:
-------------------------------

    Attachment: HDFS-472.patch

Hi Chris,
Thanks for the comments. I uploaded the new patch.

* The "advantages" and "disadvantages" in the comparison w/ H(S)FTP could be 
formatted more clearly in a list or table.
    --> yes. I listed them.
* 6.6.1 and 6.6.2 are missing a line break before the "ant clean tar" shell 
command
   --> good catch. I corrected a couple more.
* There are several occurrences of "Ip address" (e.g. 4.2.2 sub 3) that should 
read "IP address"
  --> changed
* Why are dfs.block.size and io.file.buffer.size important parameters for the 
proxy?
  --> They are not crucial to the functionality of proxy. Fine tuning these 
parameters could affect the transfer performance to some degree. This should 
have been documented in hdfs-client. 
* -There are three "hdfsproxy-default.xml" tables and all tables are labeled 
"Table 1"- (the structure is much clearer in the HTML rendering than in the 
PDF; looks like a forrest quirk)
--> seems <caption> tag inside <table> block is causing the problem. Replaced 
it with <strong> out of the <table> block. Now all look the same in HTML and 
PDF.
* Has someone unfamiliar with the details of the project successfully 
configured an instance of HDFS proxy from this documentation?
--> I did that. But maybe not fair since I am relatively familiar with it.

> Document hdfsproxy design and set-up guide
> ------------------------------------------
>
>                 Key: HDFS-472
>                 URL: https://issues.apache.org/jira/browse/HDFS-472
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: contrib/hdfsproxy
>            Reporter: zhiyong zhang
>            Assignee: zhiyong zhang
>             Fix For: 0.21.0
>
>         Attachments: HDFS-472.patch, HDFS-472.patch, hdfsproxy.pdf, 
> hdfsproxy.pdf
>
>
> currently hdfsproxy only have a README file that does not follow closely to 
> the code. Need more documentation on the design, build and set-up guide. 

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

Reply via email to