Skip to content

HDDS-15203. Clarify ozone.om.namespace.s3.strict in ozone-default.xml#10225

Merged
adoroszlai merged 1 commit into
apache:masterfrom
YutaLin:HDDS-15203_clarify_s3_namespace_restrict
May 10, 2026
Merged

HDDS-15203. Clarify ozone.om.namespace.s3.strict in ozone-default.xml#10225
adoroszlai merged 1 commit into
apache:masterfrom
YutaLin:HDDS-15203_clarify_s3_namespace_restrict

Conversation

@YutaLin
Copy link
Copy Markdown
Contributor

@YutaLin YutaLin commented May 10, 2026

What changes were proposed in this pull request?

Ozone namespace should follow S3 naming rule by default.

Suggest to update the description to "When true (the default), volume and bucket names follow strict S3 naming rules. When false, S3 rules still apply except that underscore (_) is additionally allowed in volume and bucket names; no other non-S3 characters are permitted."

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-15203

How was this patch tested?

CI (https://github.com/YutaLin/ozone/actions/runs/25615921794)

@YutaLin YutaLin marked this pull request as ready for review May 10, 2026 02:44
@adoroszlai adoroszlai merged commit 4896299 into apache:master May 10, 2026
51 of 55 checks passed
@adoroszlai
Copy link
Copy Markdown
Contributor

Thanks @YutaLin for the patch.

@YutaLin YutaLin deleted the HDDS-15203_clarify_s3_namespace_restrict branch May 10, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants