Wei-Chiu Chuang created HDDS-8292:
-------------------------------------
Summary: Inconsistent key name handling for FSO bucket files
Key: HDDS-8292
URL: https://issues.apache.org/jira/browse/HDDS-8292
Project: Apache Ozone
Issue Type: Bug
Reporter: Wei-Chiu Chuang
The definition of the field OmKeyInfo.keyName is ambiguous.
In some of the code, it is the full path to a file; in some, it is just the
final part (excluding the path).
I am looking at a cluster where some of the entries in fileTable in its OM db
has full path, and some don't.
{noformat}
# ozone debug ldb --db=om.db scan --column_family=fileTable -l -1 --with-keys |
less
"/-9223372036854561536/-9223372036854561024/-9223372036854525695/433dfbc470b54a0e9a23ed79240c3dc3"
-> {
"volumeName": "vol1",
"bucketName": "bucket1",
"keyName":
"hbase/data/hbase/meta/1588230740/info/433dfbc470b54a0e9a23ed79240c3dc3",
...
"/-9223372036854561536/-9223372036854561024/-9223372036854525695/c3a068821e7544caae7cdbaf9ca1b263"
-> {
"volumeName": "vol1",
"bucketName": "bucket1",
"keyName": "c3a068821e7544caae7cdbaf9ca1b263",
{noformat}
Bug: ListStatus request returns incorrect path name, because
OzoneListStatusHelper.getStatus() expects the keyName to be just the final
part, and prepend the prefix, which is incorrect for the example above.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
