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

Hudson commented on HBASE-25770:
--------------------------------

Results for branch branch-2.2
        [build #206 on 
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/206/]:
 (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/206//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/206//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/206//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(x) {color:red}-1 client integration test{color}
--Failed when running client tests on top of Hadoop 3. [see log for 
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/206//artifact/output-integration/hadoop-3.log].
 (note that this means we didn't check the Hadoop 3 shaded client)


> Http InfoServers should honor gzip encoding when requested
> ----------------------------------------------------------
>
>                 Key: HBASE-25770
>                 URL: https://issues.apache.org/jira/browse/HBASE-25770
>             Project: HBase
>          Issue Type: Improvement
>          Components: UI
>    Affects Versions: 2.3.0
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3, 2.3.6, 2.2.8
>
>
> Working on another project, I noticed that our InfoServer does not honor the 
> {{Accept-Encoding}} HTTP header when present. It appears to be a relatively 
> trivial matter to add the GzipHandler provided by Jetty. I'm not sure if 
> there are other encodings we should support, but this is the only one I found 
> available in Jetty itself (the other one by browser sent was "deflate").



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to