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

Andrew Purtell commented on HBASE-8345:
---------------------------------------

The patch attached here isn't versioned (therefore we presume trunk), but this 
is against 0.94, right? since I nuked 'accessToken' in HBASE-7359. 

Don't parse text when there is a structured representation, request XML or 
protobuf. Generally Remote* uses MIMETYPE_PROTOBUF. 

Why the gratuitous renames, e.g. 'sb' -> 'path'? Let's confine the changes in 
the patch to what needs to be changed.
                
> Add all available resources in o.a.h.h.rest.RootResource and VersionResource 
> to o.a.h.h.rest.client.RemoteAdmin
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8345
>                 URL: https://issues.apache.org/jira/browse/HBASE-8345
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, REST
>    Affects Versions: 0.94.6.1
>            Reporter: Aleksandr Shulman
>            Assignee: Aleksandr Shulman
>            Priority: Minor
>              Labels: rest_api
>             Fix For: 0.94.8
>
>         Attachments: HBASE-8345-v1.patch
>
>
> In our built-in REST clients, we should add in more of the available REST 
> resources. This will allow more thorough testing of the REST API, 
> particularly with IntegrationTest.
> These clients are located in the o.a.h.h.rest.client package.
> In this case, I want to add the resources not already included in / and 
> /version to o.a.h.h.rest.client.RemoteAdmin. This includes, /status/cluster, 
> /version/rest and /version/cluster, among others.
> The RemoteAdmin class is a logical place for these methods because it is not 
> related to a specific table (those methods should go into RemoteHTable).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to