[
https://issues.apache.org/jira/browse/HDDS-7586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei-Chiu Chuang updated HDDS-7586:
----------------------------------
Release Note:
Added a new configuration property:
</property>
<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>
> Allow users to create an Ozone bucket with non-s3-naming-convention
> -------------------------------------------------------------------
>
> Key: HDDS-7586
> URL: https://issues.apache.org/jira/browse/HDDS-7586
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Dave Teng
> Assignee: Dave Teng
> Priority: Major
> Labels: ozone, pull-request-available
> Fix For: 1.4.0
>
>
> To configure whether Ozone bucket's name will follow S3 naming rules or not,
> I propose to add a server side configuration 'ozone.om.namespace.s3.strict'
> in OM.
> There are two cases of the flag:
> When the config value flag is true, the bucket naming should follow S3 naming
> rules.
> When the config value flag is false, the bucket naming could choose not to
> follow S3 naming rules.
> I'd love to hear any feedback from the community!
> Thank you!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
