[ https://issues.apache.org/jira/browse/HADOOP-894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12496236 ]
Hadoop QA commented on HADOOP-894: ---------------------------------- +1 http://issues.apache.org/jira/secure/attachment/12357448/partialBlockList4.patch applied and successfully tested against trunk revision r538318. Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/148/testReport/ Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/148/console > 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 > Affects Versions: 0.12.0 > Reporter: Owen O'Malley > Assigned To: Konstantin Shvachko > Fix For: 0.13.0 > > Attachments: partialBlockList2.patch, partialBlockList3.patch, > partialBlockList4.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.