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

Hudson commented on HBASE-23245:
--------------------------------

Results for branch branch-2.2
        [build #690 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/690/]: 
(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/690//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/690//JDK8_Nightly_Build_Report_(Hadoop2)/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/690//JDK8_Nightly_Build_Report_(Hadoop3)/]


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


(/) {color:green}+1 client integration test{color}


> All MutableHistogram implementations should remove maxExpected
> --------------------------------------------------------------
>
>                 Key: HBASE-23245
>                 URL: https://issues.apache.org/jira/browse/HBASE-23245
>             Project: HBase
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 3.0.0, 2.3.0, 1.6.0
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 3.0.0, 2.3.0, 1.6.0, 1.4.12, 2.1.8, 2.2.3
>
>
> MutableHistogram is using HistogramImpl() and not using maxExpected. From all 
> implementation classes, maxExpected should be removed as constructor 
> argument. Also, HistogramImpl() should pass long casting for 
> Integer.MAX_VALUE << 2 else it is treated as -4



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

Reply via email to