You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Wei-Chiu Chuang (Jira)" <ji...@apache.org> on 2026/05/06 18:39:00 UTC
[jira] [Assigned] (HDDS-14796) [Docs] Document the effect of ozone.om.namespace.s3.strict more specifically
[ https://issues.apache.org/jira/browse/HDDS-14796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wei-Chiu Chuang reassigned HDDS-14796:
--------------------------------------
Assignee: Wei-Chiu Chuang
> [Docs] Document the effect of ozone.om.namespace.s3.strict more specifically
> ----------------------------------------------------------------------------
>
> Key: HDDS-14796
> URL: https://issues.apache.org/jira/browse/HDDS-14796
> Project: Apache Ozone
> Issue Type: Task
> Components: documentation
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
> Labels: pull-request-available
>
> {code:java}
> <property>
> <name>ozone.om.namespace.s3.strict</name>
> <value>true</value>
> <tag>OZONE, OM</tag>
> <description>
> Ozone namespace should follow S3 naming rule by default.
> However this parameter allows the namespace to support non-S3 compatible characters.
> </description>
> </property> {code}
> The wording of the description made it sound like it can support any non-S3 compatible characters; instead, when it is false, the only non-s3 compatible character allowed in underscore '_'.
>
> Similar, we should update the description in the Ozone Core Concepts doc: [https://ozone.apache.org/docs/core-concepts/namespace/buckets/overview/#what-is-a-bucket]
> {code:java}
> To relax the compliance check, configure the property ozone.om.namespace.s3.strict to false in the ozone-site.xml of Ozone Manager.{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org