[
https://issues.apache.org/jira/browse/HDFS-12147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16091136#comment-16091136
]
Nandakumar commented on HDFS-12147:
-----------------------------------
Hi [~cheersyang],
bq. Why the checkBucketAccess is exposed as a RPC call in KSM?
According to {{DistributedStorageHandler}} we are exposing
{{checkBucketAccess}}, which can be used by user to check if they have required
permission on a bucket. Similar to {{checkVolumeAccess}} for Ozone Volumes.
{code}
@Override
public void checkBucketAccess(BucketArgs args)
throws IOException, OzoneException {
throw new UnsupportedOperationException(
"checkBucketAccess not implemented");
}
{code}
bq. why we are comparing OzoneAcl?
The client has flexibility to check permission on user, group or world. So the
client has to pass {{OzoneAcl}} which will tell us on which user/group/world
and the permission that has to be checked.
Internal checks (for addBucketProperty, deleteBucket) will directly use user
name and or group name as you mentioned.
> Ozone: KSM: Add checkBucketAccess
> ---------------------------------
>
> Key: HDFS-12147
> URL: https://issues.apache.org/jira/browse/HDFS-12147
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Nandakumar
> Assignee: Nandakumar
> Attachments: HDFS-12147-HDFS-7240.000.patch,
> HDFS-12147-HDFS-7240.001.patch
>
>
> Checks if the caller has access to a given bucket.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
