You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2020/08/26 02:42:00 UTC
[jira] [Commented] (HBASE-24945) Remove
MetaTableAccessor.getRegionCount
[ https://issues.apache.org/jira/browse/HBASE-24945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184868#comment-17184868 ]
Hudson commented on HBASE-24945:
--------------------------------
Results for branch master
[build #21 on builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/21/]: (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/master/21/General_20Nightly_20Build_20Report/]
(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/master/21/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/21/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {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 2. [see log for details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/21//artifact/output-integration/hadoop-2.log]. (note that this means we didn't run on Hadoop 3)
> Remove MetaTableAccessor.getRegionCount
> ---------------------------------------
>
> Key: HBASE-24945
> URL: https://issues.apache.org/jira/browse/HBASE-24945
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce, meta
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> In fact, in the implementation of MetaTableAccessor.getRegionCount we have already switch to use RegionLocator.
> Let's just use RegionLocator directly in code.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)