[ 
https://issues.apache.org/jira/browse/HDFS-12035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16062197#comment-16062197
 ] 

Yiqun Lin commented on HDFS-12035:
----------------------------------

Thanks for reporting this, [~cheersyang]! Assign this to myself, will post the 
patch soon.

> 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
>
> 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: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to