[ 
https://issues.apache.org/jira/browse/HDDS-6574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-6574:
---------------------------------
    Labels: pull-request-available  (was: )

> Owner field of a bucket created via S3g should be set to the actual user 
> rather than "s3g"
> ------------------------------------------------------------------------------------------
>
>                 Key: HDDS-6574
>                 URL: https://issues.apache.org/jira/browse/HDDS-6574
>             Project: Apache Ozone
>          Issue Type: Task
>          Components: Ozone Client
>    Affects Versions: 1.3.0
>            Reporter: Siyao Meng
>            Assignee: Siyao Meng
>            Priority: Major
>              Labels: pull-request-available
>
> Currently if a bucket is created using S3 API via S3 Gateway, the bucket 
> owner is *always* set to "s3g" (whoever S3 Gateway authenticated itself as to 
> the Ozone Manager).
> {code:bash|title=Current behavior when a bucket is created using S3 API via 
> S3 Gateway}
> $ ozone sh bucket list /tenant1
> [ {
>   "metadata" : { },
>   "volumeName" : "s3v",
>   "name" : "bucket1",
>   "storageType" : "DISK",
>   "versioning" : false,
>   "usedBytes" : 0,
>   "usedNamespace" : 0,
>   "creationTime" : "2022-04-07T14:51:49.053Z",
>   "modificationTime" : "2022-04-07T14:51:49.053Z",
>   "quotaInBytes" : -1,
>   "quotaInNamespace" : -1,
>   "bucketLayout" : "OBJECT_STORE",
>   "owner" : "s3g",  <---
>   "link" : false
> } ]
> {code}
> This bucket owner field should be set to the user behind the accessId (short 
> name) as this should be the intended behavior.
> {code:bash|title=Expected behavior}
> $ ozone sh bucket list /tenant1
> [ {
> ...
>   "bucketLayout" : "OBJECT_STORE",
>   "owner" : "hive",  <---
>   "link" : false
> } ]
> {code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to