HDDS-15203. Clarify ozone.om.namespace.s3.strict in ozone-default.xml#10225
Merged
adoroszlai merged 1 commit intoMay 10, 2026
Merged
Conversation
adoroszlai
approved these changes
May 10, 2026
Contributor
|
Thanks @YutaLin for the patch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
ozone/hadoop-hdds/common/src/main/resources/ozone-default.xml
Line 4373 in 0f811d4
Suggest to update the description to "When
true(the default), volume and bucket names follow strict S3 naming rules. Whenfalse, 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)