[
https://issues.apache.org/jira/browse/HDDS-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17644005#comment-17644005
]
Ritesh H Shukla commented on HDDS-7585:
---------------------------------------
[[email protected]] We want the default behavior to be to prevent bucket names
that are not valid DNS names. There are some use cases for pure ofs:// based
access where the limitation on the bucket name is unintuitive as it is a path
in the URL, this in turn, leads to errors during migration from HDFS to Ozone.
One option considered here is to allow the client to intentionally create a
bucket that is not complaint, with the understanding that DNS style access to
S3 resources will not work for that bucket. That said, currently on prem
deployments rarely go with DNS style access to buckets as it needs a API
surface to be exposed by the corporate DNS server to the storage layer. Within
Kubernetes based deployments this does become easier but bare metal would be
rare.
Will look into s3a support for arn and see how we can leverage that.
> 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 enable the HDFS to Ozone
> migration with non s3 compliant paths.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
