[
https://issues.apache.org/jira/browse/HBASE-29834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18063423#comment-18063423
]
Hudson commented on HBASE-29834:
--------------------------------
Results for branch branch-2
[build #2 on
builds.a.o|https://ci-hbase.apache.org/job/HBase-Integration-Test/job/branch-2/2/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test for 2.10.2 {color}
(/) {color:green}+1 client integration test for 3.3.5 {color}
(/) {color:green}+1 client integration test for 3.3.5 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.3.6 {color}
(/) {color:green}+1 client integration test for 3.3.6 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.0 {color}
(/) {color:green}+1 client integration test for 3.4.0 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.1 {color}
(/) {color:green}+1 client integration test for 3.4.1 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.2 {color}
(/) {color:green}+1 client integration test for 3.4.2 with shaded hadoop
client{color}
(/) {color:green}+1 client integration test for 3.4.3 {color}
(/) {color:green}+1 client integration test for 3.4.3 with shaded hadoop
client{color}
> MILLIS_BETWEEN_NEXTS metric is not updated on branch-3+
> -------------------------------------------------------
>
> Key: HBASE-29834
> URL: https://issues.apache.org/jira/browse/HBASE-29834
> Project: HBase
> Issue Type: Bug
> Components: asyncclient, Client, scan
> Reporter: Istvan Toth
> Assignee: Duo Zhang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.5, 2.5.14
>
>
> It is updated in
> hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java
> on branch.2x, but it is never updated on branch-3+.
> Either restore it or deprecate it and document that it no longer works.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
