[
https://issues.apache.org/jira/browse/HBASE-28816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883928#comment-17883928
]
Hudson commented on HBASE-28816:
--------------------------------
Results for branch branch-3
[build #295 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/295/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/295/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk17 hadoop3 checks{color}
-- For more information [see jdk17
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-3/295/JDK17_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> The description of "hbase.superuser" is confusing
> -------------------------------------------------
>
> Key: HBASE-28816
> URL: https://issues.apache.org/jira/browse/HBASE-28816
> Project: HBase
> Issue Type: Improvement
> Components: documentation
> Reporter: YUBI LEE
> Assignee: YUBI LEE
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.11
>
>
> With "hbase.superuser" configuration, you can also set groups. However, it
> should be prefixed with "@" but there are no such explanation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
