[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17133150#comment-17133150
]
Hudson commented on HBASE-23896:
Results for branch branch-1
[build #1313 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1313/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1313//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1313//JDK7_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/1313//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0-alpha-1, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0-alpha-1, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090852#comment-17090852
]
Hudson commented on HBASE-23896:
Results for branch branch-2.2
[build #847 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/847/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/847//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/847//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/847//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17090194#comment-17090194
]
Guangxu Cheng commented on HBASE-23896:
---
Pushed to branch-2.2. Thanks [~wchevreuil] [~tamaas] for reivew.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089680#comment-17089680
]
Wellington Chevreuil commented on HBASE-23896:
--
LGTM, +1. Thanks for the swift response, [~gxcheng]!
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089642#comment-17089642
]
Guangxu Cheng commented on HBASE-23896:
---
I just attached an addendum patch. Could you please review it? [~wchevreuil]
[~tamaas] Thanks
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
> Attachments: HBASE-23896-branch-2.2-addendum.patch
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089633#comment-17089633
]
Guangxu Cheng commented on HBASE-23896:
---
I'm sorry for that. It’s because that getRandomUUID is not static in branch-2.2
as [~tamaas] said. I will make an addendum patch for this.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089574#comment-17089574
]
Wellington Chevreuil commented on HBASE-23896:
--
[~gxcheng], any updates on the branch-2.2 issue raised by [~tamaas]? This is
breaking branch-2.2 build.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088008#comment-17088008
]
Hudson commented on HBASE-23896:
Results for branch branch-2.2
[build #844 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/844/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/844//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/844//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/844//JDK8_Nightly_Build_Report_(Hadoop3)/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/844//console].
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087639#comment-17087639
]
Hudson commented on HBASE-23896:
Results for branch master
[build #1705 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1705/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1705/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1702/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1705/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1705/JDK11_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}
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087477#comment-17087477
]
Hudson commented on HBASE-23896:
Results for branch branch-2.3
[build #46 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/46/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/46/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/46/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/46/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/46/JDK11_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}
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087455#comment-17087455
]
Hudson commented on HBASE-23896:
Results for branch branch-2
[build #2620 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2620/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2620/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2620/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2620/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2620/JDK11_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}
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.4.0, 2.2.5
>
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-23896) Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not enabled
[
https://issues.apache.org/jira/browse/HBASE-23896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17087310#comment-17087310
]
Guangxu Cheng commented on HBASE-23896:
---
Pushed to branch-2.2+, Thanks [~binlijin] for reivew.
> Snapshot owner cannot delete snapshot when ACL is enabled and Kerberos is not
> enabled
> -
>
> Key: HBASE-23896
> URL: https://issues.apache.org/jira/browse/HBASE-23896
> Project: HBase
> Issue Type: Task
>Affects Versions: 3.0.0, 2.2.3
>Reporter: Guangxu Cheng
>Assignee: Guangxu Cheng
>Priority: Major
>
> When ACL is enabled and Kerberos is not enabled, the snapshot owner cannot
> delete the snapshot. This is because the owner of the snapshot cannot be
> taken during permission verification. By investigation, found that only after
> HBase has enabled security authentication, the owner will be set when doing
> snapshot.
> SnapshotManager#takeSnapshotInternal
> {code:title=SnapshotManager.java|borderStyle=solid}
> RpcServer.getRequestUser().ifPresent(user -> {
> if (User.isHBaseSecurityEnabled(master.getConfiguration())) {
> builder.setOwner(user.getShortName());
> }
> });
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
