[
https://issues.apache.org/jira/browse/HDDS-14795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang updated HDDS-14795:
-----------------------------------
Release Note: Bucket names are no longer required to be 3–63 characters
when strict S3 naming is disabled; the 3–63 length check is enforced only with
strict S3 enabled (volume name length validation is unchanged). (was: Bucket
name length validation (3–63 chars) is now enforced only when strict S3 naming
is enabled; when strict S3 is disabled, Ozone allows bucket names with
non-S3-compliant lengths (volume name length validation remains unchanged).)
> Allow non-S3-compliant bucket name length if strict S3 is disabled
> ------------------------------------------------------------------
>
> Key: HDDS-14795
> URL: https://issues.apache.org/jira/browse/HDDS-14795
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Sadanand Shenoy
> Assignee: Chen-Jheng Sing
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> [https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html#general-purpose-bucket-names]
> The character length criteria is supposedly derived from S3 naming rules.
> Allow creation of buckets with non-s3 compliant behaviour with posix
> compliant naming i.e length < 3 and length > 63.
> The validation for this character length check happens on the client , Move
> it to the server if the strict naming flag is enabled.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
