[jira] [Created] (HDDS-807) Do not support period as a valid character in bucket names

["Arpit Agarwal (JIRA)" <ji...@apache.org>]

Arpit Agarwal created HDDS-807:
----------------------------------

             Summary: Do not support period as a valid character in bucket names
                 Key: HDDS-807
                 URL: https://issues.apache.org/jira/browse/HDDS-807
             Project: Hadoop Distributed Data Store
          Issue Type: Improvement
            Reporter: Arpit Agarwal


ozonefs paths use the following syntax: o3fs://bucket.volume/..

The OM host and port are read from configuration.

There is no way to specify a target filesystem with a fully qualified path. E.g. _o3fs://bucket.volume.om-host.example.com:9862/. Hence there is no way we can hand a fully qualified URL with OM hostname to a client without setting up config files beforehand. This is inconvenient. It also means there is no way to perform a distcp from one Ozone cluster to another.

We need a way to support fully qualified paths with OM hostname and port _bucket.volume.om-host.example.com_. If we allow periods in bucketnames, then such fully qualified paths cannot be parsed unambiguously. However if er disallow periods, then we can support all of the following paths unambiguously.
 # *o3fs://bucket.volume/key* - The authority has only two period-separated components. These must be bucket and volume name respectively.
 # *o3fs://bucket.volume.om-host.example.com/key* - The authority has more than two components. The first two must be bucket and volume, the rest must be the hostname.
 # *o3fs://bucket.volume.om-host.example.com:5678/key* - Similar to #2, except with a port number.

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org