[
https://issues.apache.org/jira/browse/HDFS-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yiqun Lin updated HDFS-12035:
-----------------------------
Attachment: HDFS-12035-HDFS-7240.001.patch
Hi [~cheersyang], thanks for the reminder.
I have looked into the change in HDFS-11955. I think it can almost apply to
listKeys as well. But there is one minor difference that you will be better to
know.
In HDFS-12063, I did some performance improvement work and added the listKeys
in ozone client. This new method can reduce RPC calls from 3 times to just 1
time. In the original logic, we will first request one call to get volume, then
request one call get bucket under this volume, finally to put/get key in the
return bucket. Actually we don't really need to get volume, bucket. The
detailed info you can look into HDFS-12063.
Attach the initial patch. Both testing listkeys of new/old way. Please have a
review. Thanks.
> Ozone: listKey doesn't work from ozone commandline
> --------------------------------------------------
>
> Key: HDFS-12035
> URL: https://issues.apache.org/jira/browse/HDFS-12035
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Weiwei Yang
> Assignee: Yiqun Lin
> Attachments: HDFS-12035-HDFS-7240.001.patch
>
>
> HDFS-11782 implements listKey operation in KSM server side, but the
> commandline doesn't work right now,
> {code}
> ./bin/hdfs oz -listKey http://ozone1.fyre.ibm.com:9864/volume-wwei-0/bucket1/
> {code}
> gives me following output
> {noformat}
> Command Failed :
> {"httpCode":400,"shortMessage":"invalidBucketName","resource":"wwei","message":"Illegal
> max number of keys specified, the value must be in range (0, 1024], actual :
> 0.","requestID":"d1a33851-6bfa-48d2-9afc-9dd7b06dfb0e","hostName":"ozone1.fyre.ibm.com"}
> {noformat}
> I think we have following things missing
> # ListKeyHandler doesn't support common listing arguments, start, length and
> prefix.
> # Http request to {{Bucket#listBucket}} uses 0 as the default value, I think
> that's why we got "Illegal max number of keys specified" error from command
> line.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
