[HDDS-4097] S3/Ozone Filesystem inter-op

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: pull-request-available
• Target Version/s: 1.3.0
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 10/Aug/20 19:53
• Updated: 10/Jan/22 23:45
• Resolved: 10/Jan/22 23:45

Description

This Jira is to implement changes required to use Ozone buckets when data is ingested via S3 and use the bucket/volume via OzoneFileSystem. Initial implementation for this is done as part of HDDS-3955. There are few API's which have missed the changes during the implementation of HDDS-3955.

Attached design document which discusses each API, and what changes are required.

Excel sheet has information about each API, from what all interfaces the OM API is used, and what changes are required for the API to support inter-operability.

Note: The proposal for delete/rename is still under discussion, not yet finalized.

Issue Links

• is related to: HDDS-3955 Unable to list intermediate paths on keys created using S3G.
• links to: GitHub Pull Request #1411
• links to: GitHub Pull Request #1411

Sub-Tasks

• Normalize Keypath for lookupKey: Resolved
• Verify parent directories and file system semantics during initiate MPU: Resolved
• S3A Filesystem does not work with Ozone S3 in file system compat mode: Resolved
• Normalize Keypath for listKeys.: Resolved
• Enable S3 robot tests with ozone.om.enable.filesystem.paths enabled: Open