adoroszlai edited a comment on pull request #1104: URL: https://github.com/apache/hadoop-ozone/pull/1104#issuecomment-659220643
> I did some simple tests locally and looks good. Thanks @ChenSammi for that. > 1. When the source bucket is deleted, bucket link still exists. It's an expected behavior, right? Yes. > 2. (Unlike previous per-user S3 volume mapping) Link buckets are not inherently specific to a user, access is restricted only by ACL. Not very clear about what it means. would you explain it further? Previously each user had its own S3 volume and only by sharing the AWS access key could others use it. Now if you create a bucket link, other users can access it as long as ACL permits (similar to other Ozone objects). > Can we set different ACL on source bucket and bucket link? Yes. When following links eg. to create a key, only read permission is checked on the link. The source bucket is still checked for the permission required for the specific operation (eg. key list, create, or delete). > 3. We're working on Volume quota implementation. I suppose bucket link will require 0 quota from it's parent volume, only the source bucket size will be controlled by it's volume's quota, right? I'm not familiar with quotas, but I guess links should work like empty buckets in this respect. Keys are created in the source bucket, so they should not affect space usage in the link's volume. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
