[
https://issues.apache.org/jira/browse/HDDS-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jyotinder Singh updated HDDS-6683:
----------------------------------
Description:
After the post finalization, the LEGACY layout specified by the client is
overridden by the configured value of {{{}ozone.default.bucket.layout{}}}.
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 the LEGACY bucket layout type then the OM server will not
override it with the side {{ozone.default.bucket.layout}} value. This way a
client has the flexibility to create a LEGACY bucket explicitly if it doesn't
want the server configured bucket layout type.
Hint: We can use the hasBucketLayout Protobuf method to check if the field is
specified or not.
Reference: [Discussion here
|https://github.com/apache/ozone/pull/3411#issuecomment-1126550908]
was:
Presently after the post finalization, LEGACY layout specified by the client is
getting overridden by the configured value of
{{{}ozone.default.bucket.layout{}}}.
The proposal is to define a policy to override server side
{{ozone.default.bucket.layout}} bucket layout. Will introduce a SERVER_DEFAULT
enum type and client can specify explicitly SERVER_DEFAULT.
If client sends LEGACY bucket layout type then OM server will not override with
the side {{ozone.default.bucket.layout}} value. This way a client has the
flexibility to create a LEGACY bucket explicitly if he don't want server
configured bucket layout type.
If client sends SERVER_DEFAULT bucket layout type then OM server will override
it with the side {{ozone.default.bucket.layout value.}}
Reference : [Discussion here
|https://github.com/apache/ozone/pull/3411#issuecomment-1126550908]
> Introduce SERVER_DEFAULT bucket layout.
> ---------------------------------------
>
> Key: HDDS-6683
> URL: https://issues.apache.org/jira/browse/HDDS-6683
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Jyotinder Singh
> Assignee: Jyotinder Singh
> Priority: Major
>
> After the post finalization, the LEGACY layout specified by the client is
> overridden by the configured value of {{{}ozone.default.bucket.layout{}}}.
>
> 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 the LEGACY bucket layout type then the OM server will not
> override it with the side {{ozone.default.bucket.layout}} value. This way a
> client has the flexibility to create a LEGACY bucket explicitly if it doesn't
> want the server configured bucket layout type.
>
> Hint: We can use the hasBucketLayout Protobuf method to check if the field is
> specified or not.
> 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: [email protected]
For additional commands, e-mail: [email protected]
