Gargi-jais11 opened a new pull request, #11922: URL: https://github.com/apache/ozone/pull/11922
## What changes were proposed in this pull request? In FSO buckets, CreateMultipartUpload on a key that is an existing directory (for example after put-object --key dir1/) made OM return `NOT_A_FILE`, but S3 Gateway mapped it to **500 InternalError** instead of a client error. **PutObject** on the same key already returned 400 InvalidRequest with the filesystem-paths message. This change handles **NOT_A_FILE** in initializeMultipartUpload the same way as PutObject: 400 InvalidRequest and the same ozone.om.enable.filesystem.paths message for keys dir1 and dir1/. ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-17658 ## How was this patch tested? added unit test. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
