[ https://issues.apache.org/jira/browse/HBASE-22467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16850263#comment-16850263 ]
Hudson commented on HBASE-22467: -------------------------------- Results for branch branch-2.2 [build #300 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/300/]: (x) *{color:red}-1 overall{color}* ---- details (if available): (/) {color:green}+1 general checks{color} -- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/300//General_Nightly_Build_Report/] (x) {color:red}-1 jdk8 hadoop2 checks{color} -- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/300//JDK8_Nightly_Build_Report_(Hadoop2)/] (x) {color:red}-1 jdk8 hadoop3 checks{color} -- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/300//JDK8_Nightly_Build_Report_(Hadoop3)/] (/) {color:green}+1 source release artifact{color} -- See build output for details. (/) {color:green}+1 client integration test{color} > WebUI changes to enable Apache Knox UI proxying > ----------------------------------------------- > > Key: HBASE-22467 > URL: https://issues.apache.org/jira/browse/HBASE-22467 > Project: HBase > Issue Type: Improvement > Components: UI > Reporter: Josh Elser > Assignee: Josh Elser > Priority: Major > Fix For: 3.0.0, 2.1.5, 2.2.1 > > Attachments: HBASE-22467.001.patch, HBASE-22467.002.patch, > HBASE-22467.003.patch > > > Apache Knox's gateway is nice in that it can provide centralized > authentication and authorization for a collection of service. Additionally, > it can expose "private" nodes through a single point (e.g. a gateway). This > makes our life as developers much easier in cloud deployments where it's not > straightforward to access nodes (e.g. they're running on some private > network). > KNOX-1866 captures the changes over there required to make HBase's proxying > actually work (definition lives there), but there were a few things we do in > our UI which made it hard/impossible to proxy it correctly. > * ProfilerServlet was dropping extra query parameters in the URL > * JSON task output on master/regionserver couldn't be disambiguated > * Some missing /master-status and /rs-statusĀ links couldn't be disambiguated > properly due to a lack of context > * Missing content-type set on a profiler servlet response -- This message was sent by Atlassian JIRA (v7.6.3#76005)