[
https://issues.apache.org/jira/browse/HDDS-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643883#comment-17643883
]
Steve Loughran commented on HDDS-7585:
--------------------------------------
s3 and many of its clients expect the bucket name to be a valid hostname
according to whatever RFC that is. If you change that requirement then you
guarantee that the buckets will not be reachable via libraries such as the s3a
client. it will also stop you from ever exporting the buckets via virtual
hosts, as some on prem s3 servers do, as well as aws itself.
note that aws recently added an ARN syntax for s3 buckets,
https://docs.aws.amazon.com/AmazonS3/latest/userguide/s3-arn-format.html
this is designed to avoid accidental mistyping of a bucket name leading to
leaks of information; the s3a client lets you map from one of its valid bucket
names to arn references. If you implemented arn support yourselves, you could
go on to offer access to (some) invalid path names to the s3a client, hopefully
others too
> 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{*}.
> This Jira is an umbrella ticket that makes Ozone compatible with these two
> types of naming convention, both POSIX and S3, to streamline the HDFS to
> Ozone migration.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
