[
https://issues.apache.org/jira/browse/HDDS-14404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bolin Lin reassigned HDDS-14404:
--------------------------------
Assignee: Bolin Lin
> [Website v2] [Docs] [Core Concepts] Ozone Volume/Bucket name allowed
> characters
> -------------------------------------------------------------------------------
>
> Key: HDDS-14404
> URL: https://issues.apache.org/jira/browse/HDDS-14404
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: documentation
> Reporter: Wei-Chiu Chuang
> Assignee: Bolin Lin
> Priority: Major
> Labels: newbie
>
> Add a note block on volume/bucket name:
> To maintain S3 compatibility, Ozone volume and bucket name follows S3 naming
> convention.
> This means volume/bucket names in Ozone:
> * Allowed Characters and Length
> * Allowed characters: Lowercase letters (a-z), numbers (0-9), dots (.), and
> hyphens ( - ).
> * Length: Must be between 3 and 63 characters long.
> * Start and End: Must begin and end with a letter or a number.
> Prohibitions
> * Cannot contain uppercase letters or underscores (_).
> * Cannot be formatted as an IP address (e.g., 192.168.5.4).
> * Cannot have consecutive periods (e.g., my..bucket) or have dashes adjacent
> to *periods (e.g., my-.bucket).
> * Cannot end with a dash.
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
