[HDDS-8423] S3 API compatibility improvements and fixes

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 1.3.0
• Component/s: Ozone Manager, S3
• Target Version/s: 2.0.0
• Assignee: Ritesh Shukla
• Reporter: Ritesh Shukla
• Created: 14/Apr/23 22:35
• Updated: 08/Aug/24 18:19

Description

Umbrella issue for improvements to S3 API and various bucket types.

Issue Links

• is related to: HDDS-9229 [FSO] S3A compatibility - dfs -put creates dir and a file
• relates to: HDDS-9762 [FSO] Hadoop dfs s3a protocol does not work with FSO buckets
• relates to: HDDS-10399 Error when listing OBS bucket

Sub-Tasks

• Legacy buckets should return 404 for getKeyInfo: Resolved
• [FSO] S3A compatibility - dfs -mkdir creates a zero byte file instead of a directory: Resolved
• Dedicated acceptance test suite for s3a: Resolved
• Hive with s3a connector for OBS bucket hits error: Resolved
• dfs -touch creates directory instead of empty file in FSO bucket: Resolved
• S3A: parent directory not found during CompleteMPU request in FSO bucket: Resolved
• ETag change detected in S3A contract test: Resolved
• Enable ITestS3ACommitterMRJob: Resolved
• Implement multiDelete using OMKeysDeleteRequest: Resolved
• testUpdateDeepDirectoryStructureToRemote failure in OBJECT_STORE bucket: Open
• Unexpected number of files in ITestS3AContractGetFileStatusV1List: Resolved
• testRenamePopulatesDirectoryAncestors fails in FSO bucket: Change detection policy requires ETag: Open
• ITestS3AContractBulkDelete fails with FSO bucket: Open
• ITestS3AContractMkdirWithCreatePerf fails with FSO bucket: Open
• testOverwrite*EmptyDirectory fail with FSO bucket: Open