[ 
https://issues.apache.org/jira/browse/HDDS-8498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17717042#comment-17717042
 ] 

Attila Doroszlai commented on HDDS-8498:
----------------------------------------

Results with current master:

{code}
$ ozone fs -put HISTORY.md ofs://om/vol1/nonexistantbucket
put: Cannot create file under root or volume.
$ ozone fs -cp ofs://om/vol1/bucket1/test/0 ofs://om/vol2/nonexistantbucket
cp: Cannot create file under root or volume.
$ ozone fs -cp ofs://om/vol1/bucket1 ofs://om/vol2/nonexistantbucket
$ ozone fs -ls ofs://om/vol2/nonexistantbucket 
Found 1 items
drwxrwxrwx   - hadoop hadoop          0 2023-04-27 07:51 
ofs://om/vol2/nonexistantbucket/test
{code}

Behavior change is side-effect of HDDS-7586, which removed client-side 
validation of bucket name.

I think current behavior is as expected.

> "Bucket or Volume name has an unsupported character : _" On put to 
> non-existant bucket
> --------------------------------------------------------------------------------------
>
>                 Key: HDDS-8498
>                 URL: https://issues.apache.org/jira/browse/HDDS-8498
>             Project: Apache Ozone
>          Issue Type: Bug
>          Components: OM, Ozone Client
>            Reporter: Ethan Rose
>            Priority: Major
>              Labels: proton
>
> Found by Bruce Shimel (not on jira) while testing Ozone. Repro steps work in 
> docker on 
> [bee5454|https://github.com/apache/ozone/commit/bee5454d7b061ded9b4f8d20e0b2decfdc629d1a]
> {code:sh}
> $ ozone sh volume create /vol1
> $ ozone fs -put HISTORY.md ofs://om/vol1/nonexistantbucket                    
>                                                                               
>           
> put: Bucket or Volume name has an unsupported character : _ 
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to