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

Devesh Kumar Singh resolved HDDS-9649.
--------------------------------------
    Release Note: This is working as expected.
      Resolution: Not A Bug

> Ozone 'fs -mkdir' creates FSO bucket even when ozone.default.bucket.layout is 
> set to LEGACY
> -------------------------------------------------------------------------------------------
>
>                 Key: HDDS-9649
>                 URL: https://issues.apache.org/jira/browse/HDDS-9649
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: Ozone Client
>            Reporter: Jyotirmoy Sinha
>            Assignee: Devesh Kumar Singh
>            Priority: Major
>         Attachments: image-2023-11-08-13-55-28-736.png
>
>
> Ozone 'fs -mkdir' create FSO bucket even when ozone.default.bucket.layout is 
> set to LEGACY
> Config set - 
> !image-2023-11-08-13-55-28-736.png|width=666,height=142!
> Ozone fs mkdir output -
> {code:java}
> # ozone fs -mkdir ofs://ozone1/vol1/buck5
> 23/11/08 08:07:37 INFO rpc.RpcClient: Creating Bucket: vol1/buck5, with 
> bucket layout FILE_SYSTEM_OPTIMIZED, hrt_qa as owner, Versioning false, 
> Storage Type set to DISK and Encryption set to false, Replication Type set to 
> server-side default replication type, Namespace Quota set to -1, Space Quota 
> set to -1 {code}
> Ozone sh is honouring the config set -
> {code:java}
> # ozone sh bucket create vol1/buck6
> 23/11/08 08:12:38 INFO rpc.RpcClient: Creating Bucket: vol1/buck6, with 
> server-side default bucket layout, hrt_qa as owner, Versioning false, Storage 
> Type set to DISK and Encryption set to false, Replication Type set to 
> server-side default replication type, Namespace Quota set to -1, Space Quota 
> set to -1 {code}
> h4.



--
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