hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erich Hochmuth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6444) Expose the ability to set custom HTTP Request Headers for the REST client used by RemoteHTable
Date Wed, 25 Jul 2012 17:28:37 GMT

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

Erich Hochmuth commented on HBASE-6444:
---------------------------------------

That would require the following changes:
* Make the httpClient protected instead of private or provide a getter method for the member
variable
* Create an interface for the rest.Client that RemoteTable uses

I like having RemoteHTable use a rest.Client interface, i think that's a cleaner implementation
then whats there today. I'd wan't the new Client impl contributed to the HBase project. I
don't like having my application extend an HBase class to expose this functionality. I believe
this is a capability that should be part of the REST client.

                
> Expose the ability to set custom HTTP Request Headers for the REST client used by RemoteHTable
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-6444
>                 URL: https://issues.apache.org/jira/browse/HBASE-6444
>             Project: HBase
>          Issue Type: Improvement
>          Components: rest
>            Reporter: Erich Hochmuth
>         Attachments: HBASE-6444-0.94.patch, HBASE-6444.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> My corporate security office (ISO) requires that all http traffic get routed through
a Web Access Management layer (http://en.wikipedia.org/wiki/Web_access_management)
> Our Hadoop cluster has been segmented by a virtual network with all access to HBase from
outside clients being managed through HBase Stargate rest server.
> The corporate WAM system requires that all http clients authenticate with it first before
making any http request to any http service in the corporate network. After the http client
authenticates with the WAM system the WAM system returns the client a set of values that must
be inserted into a http cookie and request header of all future http requests to other http
clients.
> This would mean that all requests through the RemoteHTable interface would require that
this cookie and request header be set as part of the http request. org.apache.hadoop.hbase.rest.client.Client
looks like the appropriate place that this functionality would need to be plugged into.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message