[ 
https://issues.apache.org/jira/browse/HDFS-6874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Weiwei Yang updated HDFS-6874:
------------------------------
    Description: 
GETFILEBLOCKLOCATIONS operation is missing in HttpFS, which is already 
supported in WebHDFS.  For the request of GETFILEBLOCKLOCATIONS in 
org.apache.hadoop.fs.http.server.HttpFSServer, BAD_REQUEST is returned so far:

.......
 case GETFILEBLOCKLOCATIONS: {
        response = Response.status(Response.Status.BAD_REQUEST).build();
        break;
      }
........ 



  was:
GET_BLOCK_LOCATIONS operation is missing in HttpFS, which is already supported 
in WebHDFS.  For the request of GETFILEBLOCKLOCATIONS in 
org.apache.hadoop.fs.http.server.HttpFSServer, BAD_REQUEST is returned so far:

.......
 case GETFILEBLOCKLOCATIONS: {
        response = Response.status(Response.Status.BAD_REQUEST).build();
        break;
      }
........ 




> Add GET_BLOCK_LOCATIONS operation to HttpFS
> -------------------------------------------
>
>                 Key: HDFS-6874
>                 URL: https://issues.apache.org/jira/browse/HDFS-6874
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 2.4.1, 2.7.3
>            Reporter: Gao Zhong Liang
>            Assignee: Weiwei Yang
>              Labels: BB2015-05-TBR
>         Attachments: HDFS-6874-1.patch, HDFS-6874-branch-2.6.0.patch, 
> HDFS-6874.02.patch, HDFS-6874.03.patch, HDFS-6874.patch
>
>
> GETFILEBLOCKLOCATIONS operation is missing in HttpFS, which is already 
> supported in WebHDFS.  For the request of GETFILEBLOCKLOCATIONS in 
> org.apache.hadoop.fs.http.server.HttpFSServer, BAD_REQUEST is returned so far:
> .......
>  case GETFILEBLOCKLOCATIONS: {
>         response = Response.status(Response.Status.BAD_REQUEST).build();
>         break;
>       }
> ........ 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to