sarvekshayr commented on code in PR #419:
URL: https://github.com/apache/ozone-site/pull/419#discussion_r3200411208


##########
docs/05-administrator-guide/02-configuration/99-appendix.md:
##########
@@ -495,7 +495,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. |

Review Comment:
   The content on this page is automatically synced from the ozone repo via an 
automated workflow. To update, modify the description of this config in 
[ozone-default.xml](https://github.com/apache/ozone/blob/0f811d443ce260cb7c2dd4adb0977dada1ac0456/hadoop-hdds/common/src/main/resources/ozone-default.xml#L4373)
 first. Changes done to this page directly will be overwritten.



-- 
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]

Reply via email to