[
https://issues.apache.org/jira/browse/HBASE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421094#comment-13421094
]
Erich Hochmuth commented on HBASE-6444:
---------------------------------------
I would prefer to just use the REST client classes along with RemoteHTable for
a couple of reasons:
* So i don't maintain a fork of the entire RemoteHTable package. RemoteHTable
doesn't take an interface to a rest.Client so i can't just implement that
* If I continue to access the REST API via RemoteHTable, in the future if the
REST API changes hopefully i'll get the changes because i'm using the API from
the HBase project instead of my own client API
* We have shared code that is used in MR and Web Clients and access data via
HTableInterface so i'd be back to having to implement the whole RemoteHTable
implementation
* This seems like something that other enterprises will run into as HBase
becomes more mainstream so why not contribute back
> 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
