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

Arafat Khan resolved HDDS-11926.
--------------------------------
    Fix Version/s: 2.0.0
       Resolution: Fixed

> Inconsistency for bucket-name in bucket info between source and linked volume
> -----------------------------------------------------------------------------
>
>                 Key: HDDS-11926
>                 URL: https://issues.apache.org/jira/browse/HDDS-11926
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Jyotirmoy Sinha
>            Assignee: Jyotirmoy Sinha
>            Priority: Trivial
>              Labels: GoodForNewContributors, newbie, pull-request-available
>             Fix For: 2.0.0
>
>
> Inconsistency for bucket-name in bucket info between source and linked volume
> Bucket info of source bucket -
> {code:java}
> # ozone sh bucket info vol1/buck1
> {
>   "metadata" : { },
>   "volumeName" : "vol1",
>   "name" : "buck1",
>   "storageType" : "DISK",
>   "versioning" : false,
>   "usedBytes" : 0,
>   "usedNamespace" : 0,
>   "creationTime" : "2024-12-13T09:48:06.886Z",
>   "modificationTime" : "2024-12-13T09:48:06.886Z",
>   "sourcePathExist" : true,
>   "quotaInBytes" : -1,
>   "quotaInNamespace" : -1,
>   "bucketLayout" : "FILE_SYSTEM_OPTIMIZED",
>   "owner" : "om",
>   "link" : false
> } {code}
> Bucket info of linked bucket -
> {code:java}
> {
>   "volumeName" : "vol1link",
>   "bucketName" : "buck1link",
>   "sourceVolume" : "vol1",
>   "sourceBucket" : "buck1",
>   "creationTime" : "2024-12-13T09:48:34.096Z",
>   "modificationTime" : "2024-12-13T09:48:34.096Z",
>   "owner" : "om"
> } {code}
> In source-bucket the bucket name is marked as *_name_* whereas in linked 
> bucket its marked as {*}_bucketName_{*}.
> There should be consistency between both the json keys.



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

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

Reply via email to