[
https://issues.apache.org/jira/browse/HDDS-1927?focusedWorklogId=297516&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-297516
]
ASF GitHub Bot logged work on HDDS-1927:
----------------------------------------
Author: ASF GitHub Bot
Created on: 20/Aug/19 00:46
Start Date: 20/Aug/19 00:46
Worklog Time Spent: 10m
Work Description: bharatviswa504 commented on pull request #1263:
HDDS-1927. Consolidate add/remove Acl into OzoneAclUtil class. Contri…
URL: https://github.com/apache/hadoop/pull/1263#discussion_r315467845
##########
File path:
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/helpers/OmKeyInfo.java
##########
@@ -235,123 +231,22 @@ public FileEncryptionInfo getFileEncryptionInfo() {
return encInfo;
}
- public List<OzoneAclInfo> getAcls() {
+ public List<OzoneAcl> getAcls() {
Review comment:
`Raw protobuf class can't be extended easily for acl operations. We will
have to to wrap the acl operations anyway.`
Not understood what do you mean by wrap ACL operations anyway.
`Given the scatter logic of ACL ops for volume/bucket/key/prefix, I would
prefer to have a unified code base that can be maintained/tested easily in the
long run.`
I understand that instead of spreading logic across in multiple places keep
acl logic in single place, which can be used in all bucket/key/prefix ops. I
agree with that point. But I have not understood why same cannot be done with
protobuf acl objects.
3. Agreed thar write acl operations/ will be lesser than read Acls.
But if you think this is the right way to go, I am fine with it.
----------------------------------------------------------------
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:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 297516)
Time Spent: 3h 20m (was: 3h 10m)
> Consolidate add/remove Acl into OzoneAclUtil class
> --------------------------------------------------
>
> Key: HDDS-1927
> URL: https://issues.apache.org/jira/browse/HDDS-1927
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Xiaoyu Yao
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> This Jira is created based on @xiaoyu comment on HDDS-1884
> Can we abstract these add/remove logic into common AclUtil class as we can
> see similar logic in both bucket manager and key manager? For example,
> public static boolean addAcl(List existingAcls, OzoneAcl newAcl)
> public static boolean removeAcl(List existingAcls, OzoneAcl newAcl)
>
> But to do this, we need both OmKeyInfo and OMBucketInfo to use list of
> OzoneAcl/OzoneAclInfo.
> This Jira is to do that refactor, and also address above comment to move
> common logic to AclUtils.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
