[ https://issues.apache.org/jira/browse/HDFS-11156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15706889#comment-15706889 ]
Andrew Wang commented on HDFS-11156: ------------------------------------ I looked at the git blame, and HDFS-2527 which added the private/unstable annotation also did a rename from GETFILEBLOCKLOCATIONS to GET_BLOCK_LOCATIONS. I'm guessing it wasn't exposed initially to keep the public WebHDFS API as narrow as possible. [~szetszwo] do you have any historical perspective on this? Could you also provide more information about your usecase? Is there an out-of-tree client you are maintaining? Also, given that GET_BLOCK_LOCATIONS is effectively stable, can you just use that instead (like the Java WebHdfsFileSystem implementation)? If we do need to add a new API (which I'm okay with in the abstract), have you also considered implementing listLocatedStatus, which is IMO the better API since it returns both listing and locations in a single call? > Webhdfs rest api GET_BLOCK_LOCATIONS output doesn't comply with FileSystem API > ------------------------------------------------------------------------------ > > Key: HDFS-11156 > URL: https://issues.apache.org/jira/browse/HDFS-11156 > Project: Hadoop HDFS > Issue Type: Bug > Components: webhdfs > Affects Versions: 2.7.3 > Reporter: Weiwei Yang > Assignee: Weiwei Yang > Attachments: HDFS-11156.01.patch, HDFS-11156.02.patch, > HDFS-11156.03.patch, HDFS-11156.04.patch > > > Following webhdfs REST API > {code} > http://<HOST>:<PORT>/webhdfs/v1/<PATH>?op=GET_BLOCK_LOCATIONS&offset=0&length=1 > {code} > will get a response like > {code} > { > "LocatedBlocks" : { > "fileLength" : 1073741824, > "isLastBlockComplete" : true, > "isUnderConstruction" : false, > "lastLocatedBlock" : { ... }, > "locatedBlocks" : [ {...} ] > } > } > {code} > This represents for *o.a.h.h.p.LocatedBlocks*. However according to > *FileSystem* API, > {code} > public BlockLocation[] getFileBlockLocations(Path p, long start, long len) > {code} > clients would expect an array of BlockLocation. This mismatch should be > fixed. Marked as Incompatible change as this will change the output of the > GET_BLOCK_LOCATIONS API. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org