[jira] [Commented] (HBASE-24964) Remove MetaTableAccessor.tableExists
[
https://issues.apache.org/jira/browse/HBASE-24964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17190230#comment-17190230
]
Hudson commented on HBASE-24964:
Results for branch branch-2
[build #31 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/31/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/31//console].
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/31//console].
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/31//console].
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- Something went wrong running this stage, please [check relevant console
output|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/31//console].
(/) {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/branch-2/31//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Remove MetaTableAccessor.tableExists
>
>
> Key: HBASE-24964
> URL: https://issues.apache.org/jira/browse/HBASE-24964
> Project: HBase
> Issue Type: Sub-task
> Components: meta
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> At master side, we could make use of TableDescriptors to determine whether a
> table exists, as it caches all the table descriptors.
> For other places, we could just make use Admin.tableExists, which is exactly
> the same with calling MetaTableAccessor.tableExists but avoid exposing meta
> directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24964) Remove MetaTableAccessor.tableExists
[
https://issues.apache.org/jira/browse/HBASE-24964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17189217#comment-17189217
]
Hudson commented on HBASE-24964:
Results for branch master
[build #32 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/32/]:
(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/32/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/32/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/32/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/32//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Remove MetaTableAccessor.tableExists
>
>
> Key: HBASE-24964
> URL: https://issues.apache.org/jira/browse/HBASE-24964
> Project: HBase
> Issue Type: Sub-task
> Components: meta
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> At master side, we could make use of TableDescriptors to determine whether a
> table exists, as it caches all the table descriptors.
> For other places, we could just make use Admin.tableExists, which is exactly
> the same with calling MetaTableAccessor.tableExists but avoid exposing meta
> directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24964) Remove MetaTableAccessor.tableExists
[ https://issues.apache.org/jira/browse/HBASE-24964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17188253#comment-17188253 ] Duo Zhang commented on HBASE-24964: --- Let me check... > Remove MetaTableAccessor.tableExists > > > Key: HBASE-24964 > URL: https://issues.apache.org/jira/browse/HBASE-24964 > Project: HBase > Issue Type: Sub-task > Components: meta >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > At master side, we could make use of TableDescriptors to determine whether a > table exists, as it caches all the table descriptors. > For other places, we could just make use Admin.tableExists, which is exactly > the same with calling MetaTableAccessor.tableExists but avoid exposing meta > directly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24964) Remove MetaTableAccessor.tableExists
[
https://issues.apache.org/jira/browse/HBASE-24964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187806#comment-17187806
]
Hudson commented on HBASE-24964:
Results for branch branch-2
[build #28 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/28/]:
(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/28/General_20Nightly_20Build_20Report/]
(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/28/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(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/28/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/28/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/branch-2/28//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Remove MetaTableAccessor.tableExists
>
>
> Key: HBASE-24964
> URL: https://issues.apache.org/jira/browse/HBASE-24964
> Project: HBase
> Issue Type: Sub-task
> Components: meta
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> At master side, we could make use of TableDescriptors to determine whether a
> table exists, as it caches all the table descriptors.
> For other places, we could just make use Admin.tableExists, which is exactly
> the same with calling MetaTableAccessor.tableExists but avoid exposing meta
> directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-24964) Remove MetaTableAccessor.tableExists
[ https://issues.apache.org/jira/browse/HBASE-24964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187771#comment-17187771 ] Viraj Jasani commented on HBASE-24964: -- [~zhangduo] On branch-2, TestMetaTableMetrics#testMetaTableMetricsInJmx is failing after this patch, seems meta table metrics mismatch. > Remove MetaTableAccessor.tableExists > > > Key: HBASE-24964 > URL: https://issues.apache.org/jira/browse/HBASE-24964 > Project: HBase > Issue Type: Sub-task > Components: meta >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0-alpha-1, 2.4.0 > > > At master side, we could make use of TableDescriptors to determine whether a > table exists, as it caches all the table descriptors. > For other places, we could just make use Admin.tableExists, which is exactly > the same with calling MetaTableAccessor.tableExists but avoid exposing meta > directly. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (HBASE-24964) Remove MetaTableAccessor.tableExists
[
https://issues.apache.org/jira/browse/HBASE-24964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17187358#comment-17187358
]
Hudson commented on HBASE-24964:
Results for branch master
[build #28 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/28/]:
(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/28/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/28/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/master/28/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/28//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Remove MetaTableAccessor.tableExists
>
>
> Key: HBASE-24964
> URL: https://issues.apache.org/jira/browse/HBASE-24964
> Project: HBase
> Issue Type: Sub-task
> Components: meta
>Reporter: Duo Zhang
>Assignee: Duo Zhang
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.4.0
>
>
> At master side, we could make use of TableDescriptors to determine whether a
> table exists, as it caches all the table descriptors.
> For other places, we could just make use Admin.tableExists, which is exactly
> the same with calling MetaTableAccessor.tableExists but avoid exposing meta
> directly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
