[
https://issues.apache.org/jira/browse/HBASE-25073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17200918#comment-17200918
]
Hudson commented on HBASE-25073:
--------------------------------
Results for branch branch-2.2
[build #68 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/68/]:
(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/68//General_Nightly_Build_Report/]
(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.2/68//console].
(/) {color:green}+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/68//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 2. [see log for
details|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2.2/68//artifact/output-integration/hadoop-2.log].
(note that this means we didn't run on Hadoop 3)
> Should not use XXXService.Interface.class.getSimpleName as stub key prefix in
> AsyncConnectionImpl
> -------------------------------------------------------------------------------------------------
>
> Key: HBASE-25073
> URL: https://issues.apache.org/jira/browse/HBASE-25073
> Project: HBase
> Issue Type: Task
> Components: Client
> Reporter: Duo Zhang
> Assignee: wangwei
> Priority: Major
> Labels: beginner, trivial
> Fix For: 3.0.0-alpha-1, 2.3.3, 2.4.0, 2.2.7
>
>
> It will just return "Interface" for all services. This is not a bug for
> AsyncConnectionImpl as we have different maps for ClientService and
> AdminService, but it is still a bit confusing to developers.
> I suggest either we just use empty string and add a comment to say that the
> service name is not important here, or change to use
> XXXService.class.getSimpleName() or XXXService.getDescriptor().getName(), so
> it is less confusing to developers.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
