[
https://issues.apache.org/jira/browse/HADOOP-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493433
]
Hadoop QA commented on HADOOP-894:
----------------------------------
-1, new javadoc warnings
The javadoc tool appears to have generated warning messages when testing the
latest attachment
http://issues.apache.org/jira/secure/attachment/12356609/partialBlockList.patch
against trunk revision r534624.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/111/testReport/
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/111/console
Please note that this message is automatically generated and may represent a
problem with the automation system and not the patch.
> dfs client protocol should allow asking for parts of the block map
> ------------------------------------------------------------------
>
> Key: HADOOP-894
> URL: https://issues.apache.org/jira/browse/HADOOP-894
> Project: Hadoop
> Issue Type: Improvement
> Components: dfs
> Reporter: Owen O'Malley
> Assigned To: Konstantin Shvachko
> Fix For: 0.13.0
>
> Attachments: partialBlockList.patch
>
>
> I think that the HDFS client protocol should change like:
> /** The meta-data about a file that was opened. */
> class OpenFileInfo {
> /** the info for the first block */
> public LocatedBlockInfo getBlockInfo();
> public long getBlockSize();
> public long getLength();
> }
> interface ClientProtocol extends VersionedProtocol {
> public OpenFileInfo open(String name) throws IOException;
> /** get block info for any range of blocks */
> public LocatedBlockInfo[] getBlockInfo(String name, int blockOffset, int
> blockLength) throws IOException;
> }
> so that the client can decide how much block info to request and when.
> Currently, when the file is opened or an error occurs, the entire block list
> is requested and sent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
