[
https://issues.apache.org/jira/browse/HDDS-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17678435#comment-17678435
]
Dave Teng commented on HDDS-7585:
---------------------------------
The following actions in Ozone involves checking the name convention of a
bucket (specifically, you can find from [this
RpcClient|https://github.com/apache/ozone/blob/master/hadoop-ozone/client/src/main/java/org/apache/hadoop/ozone/client/rpc/RpcClient.java]
class):
- create Bucket
- set Bucket Storage Type
- set Replication Config
- set Bucket Owner
- get Bucket Details
- delete Bucket
- create Key
- get Key
- get Key metadata
- delete Key
- rename Key
- initiate/create/abort MultipartKey
- head S3 Object
- head Object
> 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: [email protected]
For additional commands, e-mail: [email protected]
