You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Rakesh Radhakrishnan (Jira)" <ji...@apache.org> on 2022/06/03 15:09:00 UTC
[jira] [Resolved] (HDDS-6683) Refactor OM server bucket layout configuration usage
[ https://issues.apache.org/jira/browse/HDDS-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rakesh Radhakrishnan resolved HDDS-6683.
----------------------------------------
Fix Version/s: 1.3.0
Resolution: Fixed
> Refactor OM server bucket layout configuration usage
> ----------------------------------------------------
>
> Key: HDDS-6683
> URL: https://issues.apache.org/jira/browse/HDDS-6683
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Jyotinder Singh
> Assignee: Tanvi Penumudy
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.3.0
>
>
> After the post finalization, user should be able to create LEGACY, FSO, OBS layouts.
>
> The proposal is to modify the behavior on the server-side to only use the {{ozone.default.bucket.layout}} config if the client has not specified any bucket layout in the protobuf message.
> If the client sends LEGACY bucket layout type then OM server will not override it with {{ozone.default.bucket.layout}} config value. This way a client has the flexibility to create a LEGACY bucket explicitly.
> Hint: We can use the {{bucketInfo.hasBucketLayout()}} Protobuf method to check if the field is set by the user.
> Reference: [Discussion here |https://github.com/apache/ozone/pull/3411#issuecomment-1126550908]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org