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

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: fs/azure
• Assignee: Steve Loughran
• Reporter: Steve Loughran
• Created: 16/Nov/17 19:36
• Updated: 21/Jan/21 13:48
• Resolved: 21/Jan/21 13:48

Description

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

Issue Links

• Is contained by: HADOOP-14943 Add common getFileBlockLocations() emulation for object stores, including S3A