[
https://issues.apache.org/jira/browse/HDDS-7577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17685628#comment-17685628
]
Siyao Meng commented on HDDS-7577:
----------------------------------
bq. doc attached to the jira looks to support displaying object owner to s3
clients
oh..
bq. If we store user name we cannot return the access ID, however if we store
access ID we could still do the conversion to user name for acl checks.
True. We could. But I worry that breaking the pattern by storing access ID
instead of user name in keys' owner field would raise other issues that we
haven't thought of:
1. What to store for the keys when a volume is not a regular non-tenant volume?
Should be user name right?
2. What happens when we delete the tenant? The tenant volume/buckets/keys still
remains. All the key owner fields becomes invalid.
It might be much better to just add a new optional field called
{{ownerAccessId}} in {{OmKeyInfo}} for this purpose, which can be passed to S3
clients.
> Add Key owner field
> -------------------
>
> Key: HDDS-7577
> URL: https://issues.apache.org/jira/browse/HDDS-7577
> Project: Apache Ozone
> Issue Type: New Feature
> Components: Ozone Manager
> Reporter: ChenXi
> Assignee: ChenXi
> Priority: Major
>
> https://docs.google.com/document/d/1NwnfxPQCUwP-CV8RjerKeuR3puFiOsxjKBxP8rE6P2k/edit?usp=sharing
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
