[
https://issues.apache.org/jira/browse/HDDS-8292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17705780#comment-17705780
]
Wei-Chiu Chuang commented on HDDS-8292:
---------------------------------------
for example, the following ListStatus request for directory
hbase/data/hbase/meta/1588230740/info
{noformat}
2023-03-28 00:29:03,829 TRACE org.apache.hadoop.ipc.ProtobufRpcEngine: 188:
Call -> ozpc12-cf4-3.ozpc12-cf4.root.hwx.site/172.27.187.137:9862:
submitRequest {cmdType: ListStatus traceID: "" clientId: "client-4413CB9AFB1A"
version: 3 listStatusRequest { keyArgs { volumeName: "vol1" bucketName:
"bucket1" keyName: "hbase/data/hbase/meta/1588230740/info" sortDatanodes: false
latestVersionLocation: true } recursive: false startKey: "" numEntries: 1024 }}
{noformat}
returns the path name
hbase/data/hbase/meta/1588230740/info/hbase/data/hbase/meta/1588230740/info/433dfbc470b54a0e9a23ed79240c3dc3
{noformat}
2023-03-28 00:29:03,839 TRACE org.apache.hadoop.ipc.ProtobufRpcEngine: 188:
Response <- ozpc12-cf4-3.ozpc12-cf4.root.hwx.site/172.27.187.137:9862:
submitRequest {cmdType: ListStatus traceID: "" success: true status: OK
listStatusResponse { statuses { keyInfo { volumeName: "vol1" bucketName:
"bucket1" keyName:
"hbase/data/hbase/meta/1588230740/info/hbase/data/hbase/meta/1588230740/info/433dfbc470b54a0e9a23ed79240c3dc3"
.....
{noformat}
“hbase/data/hbase/meta/1588230740/info/hbase/data/hbase/meta/1588230740/info/433dfbc470b54a0e9a23ed79240c3dc3”
notice that the prefix is erroneously prepended twice.
> 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
> Affects Versions: 1.4.0
> Reporter: Wei-Chiu Chuang
> Priority: Major
>
> 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]
