Russole opened a new pull request, #9462: URL: https://github.com/apache/ozone/pull/9462
## What changes were proposed in this pull request? This patch limits the non-strict naming behavior only to FSO buckets, which do not rely on S3 naming semantics. Legacy/ObjectStore buckets—which represent the S3 bucket layout in Ozone—continue to enforce strict, S3-compliant naming rules, even when strict mode is disabled. In summary, this PR ensures that only FSO buckets may use non-strict bucket names when ozone.om.namespace.s3.strict=false; S3 buckets (Legacy/ObjectStore) must remain strict. ## Appoach * Updated OMBucketCreateRequest to apply non-strict bucket name validation only when strict mode is disabled and the bucket layout is FSO. * Ensured that S3 buckets (Legacy/ObjectStore layout) always enforce strict, S3-compliant naming rules, regardless of the strict-mode setting. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-8511 ## How was this patch tested? I relied on existing unit and integration tests, and verified that the full CI passed on my fork. Please let me know if additional tests are needed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
