Dave Teng created HDDS-7809:
-------------------------------
Summary: Allow Ozone Volume to use non-S3-compliance characters
Key: HDDS-7809
URL: https://issues.apache.org/jira/browse/HDDS-7809
Project: Apache Ozone
Issue Type: Improvement
Components: Ozone Filesystem, Ozone Manager
Reporter: Dave Teng
We notice many HDFS migration cases which translate the first level directory
names to Ozone volume 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 volume via Ozone CLI, Ozone will allow
*underscore*_ only for such volumes. The idea is it'd be user's choice whether
to create a non-s3 naming compliant volume or not. Ozone will keep equally
supporting both kinds of volume. For pure file system back ground users, they
may want to go ahead to use this flag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
