[jira] [Comment Edited] (HADOOP-15044) Wasb getFileBlockLocations() returns too many locations.

["Steve Loughran (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-15044?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16255845#comment-16255845 ] 

Steve Loughran edited comment on HADOOP-15044 at 11/16/17 7:39 PM:
-------------------------------------------------------------------

+[~tmarquardt]. 

Found this when merging the wasb logic with that I was adding for HADOOP-14043: you always get the #of blocks in the file, irrespective of offset or length. Will be fixed in that patch


was (Author: stevel@apache.org):
+[~tmarquardt]. 

Found this when merging the wasb logic with that I was adding for HADOOP-14393: you always get the #of blocks in the file, irrespective of offset or length. Will be fixed in that patch

> Wasb getFileBlockLocations() returns too many locations.
> --------------------------------------------------------
>
>                 Key: HADOOP-15044
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15044
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/azure
>            Reporter: Steve Loughran
>
> The wasb mimicking of {{getFileBlockLocations()}} uses the length of the file as the number to use to calculate the # of blocks to create (i.e. file.length/blocksize), when it should be just the range of the request.
> As a result, you always get the number of blocks in the total file, not the number spanning the range of (start, len). If this is less (i.e start > 0 or len < file.length), you end up with some 0-byte-range blocks at the end



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org