[HDDS-4102] Normalize Keypath for lookupKey

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: pull-request-available
• Target Version/s: 1.1.0
• Assignee: Bharat Viswanadham
• Reporter: Bharat Viswanadham
• Created: 11/Aug/20 18:02
• Updated: 28/Sep/20 18:29
• Resolved: 28/Sep/20 18:29

Description

When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the Keyname.

Now when user tries to read the file from S3 using the keyName which user has used to create the Key, it will return error KEY_NOT_FOUND

The issue is, lookupKey need to normalize path, when ozone.om.enable.filesystem.paths is enabled. This is common API used by S3/FS.

Issue Links

• is cloned by: HDDS-4117 Normalize Keypath for listKeys.
• links to: GitHub Pull Request #1315
• links to: GitHub Pull Request #1328