[jira] [Commented] (HDDS-10840) Determine how ownership of keys overwritten using the atomic commit API should work

["Stephen O'Donnell (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDDS-10840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17847903#comment-17847903 ] 

Stephen O'Donnell commented on HDDS-10840:
------------------------------------------

Upon reviewing the code, the "owner" field is only set at the OM server side when a new key is created. In the case a key is overwritten, the owner is never retrieved from the keyargs and hence overwriting the owner when overwriting a key is not possible. This is the case, both prior to the atomic key overwrite feature and when the traditional key overwrite where a new version is allocated.

Therefore this change should simply remove the owner details from being passed in the rewrite key and the owner will continue to be inherited as it is now.

> Determine how ownership of keys overwritten using the atomic commit API should work
> -----------------------------------------------------------------------------------
>
>                 Key: HDDS-10840
>                 URL: https://issues.apache.org/jira/browse/HDDS-10840
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: OM
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>
> As per this comment:
> https://github.com/apache/ozone/pull/6385#discussion_r1594869863
> We need to decide how ownership of keys overwritten should work. Probably it is best to let them be owned by their original owner, rather than a possible Admin user who rewrites them.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org