[
https://issues.apache.org/jira/browse/HDDS-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-4117:
-------------------------------------
Description:
When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the
Keyname.
When listKeys uses given keyName(not normalized key path) as prefix and Starkey
the list-keys will return empty result.
Similar to HDDS-4102, we should normalize startKey and keyPrefix.
was:
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.
> Normalize Keypath for listKeys.
> --------------------------------
>
> Key: HDDS-4117
> URL: https://issues.apache.org/jira/browse/HDDS-4117
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
>
> When ozone.om.enable.filesystem.paths, OM normalizes path, and stores the
> Keyname.
> When listKeys uses given keyName(not normalized key path) as prefix and
> Starkey the list-keys will return empty result.
> Similar to HDDS-4102, we should normalize startKey and keyPrefix.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
