You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Sammi Chen (Jira)" <ji...@apache.org> on 2023/01/05 03:21:00 UTC
[jira] [Comment Edited] (HDDS-7585) Allow Ozone bucket to use non-S3-compliance naming rule
[ https://issues.apache.org/jira/browse/HDDS-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654716#comment-17654716 ]
Sammi Chen edited comment on HDDS-7585 at 1/5/23 3:20 AM:
----------------------------------------------------------
How about this simple solution. Say we introduce a global boolean configuration, such as "posix.compliant". Default it's false, ozone will reject any bucket name with "_{_}". If it's true, Ozone will dynamically convert "_{_}" to "-" in any bucket access. This way, every bucket saved in Ozone still follow the s3 naming rule, while we provide the posix compliant on API level once the new property is true.
was (Author: sammi):
How about this simple solution. Say we introduce a global boolean configuration, such as "posix.compliant". Default it's false, ozone will reject any bucket name with "_". If it's true, Ozone will dynamically convert "_" to "-" in any bucket access. This way, every bucket saved in Ozone still follow the s3 naming rule, while we provide the posix compliant on API level once the new property is true.
> Allow Ozone bucket to use non-S3-compliance naming rule
> -------------------------------------------------------
>
> Key: HDDS-7585
> URL: https://issues.apache.org/jira/browse/HDDS-7585
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone CLI, Ozone Filesystem, Ozone Manager
> Reporter: Dave Teng
> Priority: Major
>
> We notice many HDFS migration cases which translate the second level directory names to Ozone bucket names.
> However, some characters in the name of directory are +compliant with POSIX+ convention, but are +not compliant with S3+ naming rule, such as {*}underscore{*}.
> Thus the original HDFS path which contains *underscore* _character are not allowed to put into Ozone because by default Ozone's path validation is same as S3. For such users, this proposal wish to provide a way that when the user gives a flag while creating the bucket via Ozone CLI (not from S3 interface), Ozone will allow *underscore*_ only for such buckets. The idea is it'd be user's choice whether to create a non-s3 compliant bucket path or not. Ozone will keep equally supporting both OFS and S3 interfaces. For pure file system back ground users, they may want to go ahead with this flag by having the awareness of that they may not be able to access the bucket through S3 interface.
>
> This Jira is an umbrella ticket that makes Ozone compatible with these two types of naming convention, both POSIX and S3, to enable the HDFS to Ozone migration with non s3 compliant paths.
>
> (ps:
> - This proposal wouldn't change the default behavior of S3 bucket naming semantic in Ozone.
> - The documentation for new flag will be provided! )
>
--
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