[HDDS-7922] [FSO] S3G folder support fso layout filestatus s3A compatibility

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Labels: pull-request-available
• Assignee: Mladjan Gadzic
• Reporter: Neil Joshi
• Created: 08/Feb/23 04:40
• Updated: 30/Jun/23 20:51
• Resolved: 30/Jun/23 20:51

Description

Currently there exists an incompatibility with file stats issued with s3a adapter through s3-gateway on directories created with fso layout.  

S3a expects file status (exist) queries on directories issued through s3 gateway to have path names ending with a '/' slash.  The s3gateway returns directory exists on directory paths with and without a trailing slash due to internal path normalization (eg. path/dir1 == path/dir1/).

 

File exists, file status is queried by s3A over s3gateway with Head requests (head-object s3 requests).  Proposed is an implementation to resolve the issue and to cover corner cases to support fso folders over s3g by modifying the s3g ObjectEndpoint to check whether the requested path is a directory, if so, to only return ok if path has trailing '/'.  This would support s3 Head requests and Get requests.  The type of object, where file or directory is determined in the head-object and get-object request through checking the keyInfo (modifying the OzoneKey and OzoneKeyDetails) isFile().

 

A sample sequence diagram for this is attached.    

 

Issue Links

• is related to: HDDS-8424 Legacy buckets should return 404 for getKeyInfo
• links to: GitHub Pull Request #4448