This is an automated email from the ASF dual-hosted git repository.
jojochuang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ozone-site.git
The following commit(s) were added to refs/heads/master by this push:
new 91968428b HDDS-14796. Document ozone.om.namespace.s3.strict
underscore-only relaxation (#419)
91968428b is described below
commit 91968428bfa74cb666b620a1c2585d08a7f4ffe2
Author: Wei-Chiu Chuang <[email protected]>
AuthorDate: Thu May 7 11:56:38 2026 -0700
HDDS-14796. Document ozone.om.namespace.s3.strict underscore-only
relaxation (#419)
Generated-by: Cursor composer-2-fast
---
docs/03-core-concepts/03-namespace/01-volumes/01-overview.md | 2 +-
docs/03-core-concepts/03-namespace/02-buckets/01-overview.md | 2 +-
docs/05-administrator-guide/02-configuration/99-appendix.md | 2 +-
.../03-core-concepts/03-namespace/01-volumes/01-overview.md | 2 +-
.../03-core-concepts/03-namespace/02-buckets/01-overview.md | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/docs/03-core-concepts/03-namespace/01-volumes/01-overview.md
b/docs/03-core-concepts/03-namespace/01-volumes/01-overview.md
index da89a0449..e34f2b8b4 100644
--- a/docs/03-core-concepts/03-namespace/01-volumes/01-overview.md
+++ b/docs/03-core-concepts/03-namespace/01-volumes/01-overview.md
@@ -35,7 +35,7 @@ Prohibitions:
This can cause trouble when migrating HDFS workloads to Ozone, since HDFS path
names are POSIX-compliant.
-To relax the compliance check, configure the property
`ozone.om.namespace.s3.strict` to `false` in the `ozone-site.xml` of Ozone
Manager.
+To allow underscore (`_`) in volume and bucket names while still enforcing the
other S3 naming rules, configure the property `ozone.om.namespace.s3.strict` to
`false` in the `ozone-site.xml` of Ozone Manager. (This does not relax the
rules for other non-S3 characters.)
:::
diff --git a/docs/03-core-concepts/03-namespace/02-buckets/01-overview.md
b/docs/03-core-concepts/03-namespace/02-buckets/01-overview.md
index 51376f64e..6bab44394 100644
--- a/docs/03-core-concepts/03-namespace/02-buckets/01-overview.md
+++ b/docs/03-core-concepts/03-namespace/02-buckets/01-overview.md
@@ -36,7 +36,7 @@ Prohibitions:
This can cause trouble when migrating HDFS workloads to Ozone, since HDFS path
names are POSIX-compliant.
-To relax the compliance check, configure the property
`ozone.om.namespace.s3.strict` to `false` in the `ozone-site.xml` of Ozone
Manager.
+To allow underscore (`_`) in volume and bucket names while still enforcing the
other S3 naming rules, configure the property `ozone.om.namespace.s3.strict` to
`false` in the `ozone-site.xml` of Ozone Manager. (This does not relax the
rules for other non-S3 characters.)
:::
diff --git a/docs/05-administrator-guide/02-configuration/99-appendix.md
b/docs/05-administrator-guide/02-configuration/99-appendix.md
index e18ec6cb5..bfc5fb34c 100644
--- a/docs/05-administrator-guide/02-configuration/99-appendix.md
+++ b/docs/05-administrator-guide/02-configuration/99-appendix.md
@@ -496,7 +496,7 @@ This page provides a comprehensive overview of the
configuration keys available
| `ozone.om.multitenancy.enabled` | false | `OZONE`, `OM` | Enable S3
Multi-Tenancy. If disabled, all S3 multi-tenancy requests are rejected. |
| `ozone.om.multitenancy.ranger.sync.interval` | 10m | `OZONE`, `OM` |
Determines how often the Multi-Tenancy Ranger background sync thread service
should run. Background thread periodically checks Ranger policies and roles
created by Multi-Tenancy feature. And overwrites them if obvious discrepancies
are detected. Value should be set with a unit suffix (ns,ms,s,m,h,d) |
| `ozone.om.multitenancy.ranger.sync.timeout` | 10s | `OZONE`, `OM` | The
timeout for each Multi-Tenancy Ranger background sync thread run. If the
timeout has been reached, a warning message will be logged. |
-| `ozone.om.namespace.s3.strict` | true | `OZONE`, `OM` | Ozone namespace
should follow S3 naming rule by default. However this parameter allows the
namespace to support non-S3 compatible characters. |
+| `ozone.om.namespace.s3.strict` | true | `OZONE`, `OM` | 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. |
| `ozone.om.network.topology.refresh.duration` | 1h | `SCM`, `OZONE`, `OM` |
The duration at which we periodically fetch the updated network topology
cluster tree from SCM. |
| `ozone.om.node.id` | | `OM`, `HA` | The ID of this OM node. If the OM node
ID is not configured it is determined automatically by matching the local
node's address with the configured address. If node ID is not deterministic
from the configuration, then it is set to default node id - om1. |
| `ozone.om.nodes.EXAMPLEOMSERVICEID` | | `OM`, `HA` | Comma-separated list
of OM node Ids for a given OM service ID (eg. EXAMPLEOMSERVICEID). The OM
service ID should be the value (one of the values if there are multiple) set
for the parameter `ozone.om.service.ids`. Decommissioned nodes (represented by
node Ids in ozone.om.decommissioned.nodes config list) will be ignored and not
included in the OM HA setup even if added to this list. Unique identifiers for
each OM Node, delimited by [...]
diff --git
a/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/01-volumes/01-overview.md
b/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/01-volumes/01-overview.md
index da89a0449..e34f2b8b4 100644
---
a/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/01-volumes/01-overview.md
+++
b/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/01-volumes/01-overview.md
@@ -35,7 +35,7 @@ Prohibitions:
This can cause trouble when migrating HDFS workloads to Ozone, since HDFS path
names are POSIX-compliant.
-To relax the compliance check, configure the property
`ozone.om.namespace.s3.strict` to `false` in the `ozone-site.xml` of Ozone
Manager.
+To allow underscore (`_`) in volume and bucket names while still enforcing the
other S3 naming rules, configure the property `ozone.om.namespace.s3.strict` to
`false` in the `ozone-site.xml` of Ozone Manager. (This does not relax the
rules for other non-S3 characters.)
:::
diff --git
a/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/02-buckets/01-overview.md
b/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/02-buckets/01-overview.md
index 51376f64e..6bab44394 100644
---
a/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/02-buckets/01-overview.md
+++
b/versioned_docs/version-2.1.0/03-core-concepts/03-namespace/02-buckets/01-overview.md
@@ -36,7 +36,7 @@ Prohibitions:
This can cause trouble when migrating HDFS workloads to Ozone, since HDFS path
names are POSIX-compliant.
-To relax the compliance check, configure the property
`ozone.om.namespace.s3.strict` to `false` in the `ozone-site.xml` of Ozone
Manager.
+To allow underscore (`_`) in volume and bucket names while still enforcing the
other S3 naming rules, configure the property `ozone.om.namespace.s3.strict` to
`false` in the `ozone-site.xml` of Ozone Manager. (This does not relax the
rules for other non-S3 characters.)
:::
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
