[
https://issues.apache.org/jira/browse/HDFS-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16066736#comment-16066736
]
Weiwei Yang commented on HDFS-12030:
------------------------------------
Hi [~linyiqun]
I see. I actually was expecting something like your v1 patch as that respects
the API design. But I doubt if getKey would still work if you give a default
value to query parameter "info"
{code}
+ @DefaultValue(Header.OZONE_LIST_QUERY_KEY)
+ @QueryParam(Header.OZONE_LIST_QUERY_TAG)
{code}
you may want to double check.
bq. I am thinking if there is one way we can handle this in different processor
meanwhile keep the url path not changed?
As far as I know the http request is dispatched to java handlers only by the
*path*, not parameters. So probably if the GET requests use same path, they
will be always routed to one handler. I am not sure how to address [~xyao]'s
comment in such case, maybe he can us a hint.
> Ozone: CLI: support infoKey command
> -----------------------------------
>
> Key: HDFS-12030
> URL: https://issues.apache.org/jira/browse/HDFS-12030
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Xiaoyu Yao
> Assignee: Yiqun Lin
> Attachments: HDFS-12030-HDFS-7240.001.patch,
> HDFS-12030-HDFS-7240.002.patch, HDFS-12030-HDFS-7240.003.patch
>
>
> {code}
> HW11717:ozone xyao$ hdfs oz -infoKey
> http://localhost:9864/vol-2/bucket-1/key-1 -user xyao
> Command Failed : {"httpCode":0,"shortMessage":"Not supported
> yet","resource":null,"message":"Not supported
> yet","requestID":null,"hostName":null}
> {code}
--
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
