[
https://issues.apache.org/jira/browse/HBASE-6444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429311#comment-13429311
]
Hadoop QA commented on HBASE-6444:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12539318/trunk-6444_v2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The applied patch generated 5 javac compiler warnings (more than
the trunk's current 4 warnings).
-1 findbugs. The patch appears to introduce 9 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop2-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop1-compat.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-hadoop-compat.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/2520//console
This message is automatically generated.
> 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
> Assignee: Jimmy Xiang
> Attachments: HBASE-6444-0.94.patch, HBASE-6444.patch,
> trunk-6444.patch, trunk-6444_v2.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
