[
https://issues.apache.org/jira/browse/HDFS-11955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16043881#comment-16043881
]
Weiwei Yang commented on HDFS-11955:
------------------------------------
Hi [~anu]
Thanks for the quick response. I haven't tested this yet, but I noticed
{code}
@GET
@Produces(MediaType.APPLICATION_JSON)
Response listBucket(@PathParam("volume") String volume,
@PathParam("bucket") String bucket,
@DefaultValue(Header.OZONE_LIST_QUERY_KEY)
@QueryParam(Header.OZONE_LIST_QUERY_TAG)
String info,
@QueryParam(Header.OZONE_LIST_QUERY_PREFIX)
String prefix,
@QueryParam(Header.OZONE_LIST_QUERY_MAXKEYS)
int maxKeys,
@QueryParam(Header.OZONE_LIST_QUERY_PREVKEY)
String prevKey,
@Context Request req, @Context UriInfo uriInfo,
@Context HttpHeaders headers) throws OzoneException;
{code}
I did not see default values for {{OZONE_LIST_QUERY_MAXKEYS}}, that gonna
probably set to 0? I will test and make sure everything works for rest calls.
> Ozone: Set proper parameter default values for listBuckets http request
> -----------------------------------------------------------------------
>
> Key: HDFS-11955
> URL: https://issues.apache.org/jira/browse/HDFS-11955
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
>
> HDFS-11779 implements the listBuckets function in ozone server side, the API
> supports several parameters, startKey, count and prefix. But both of them are
> optional for the client side rest API. This jira is to make sure we set
> proper default values in the http request if they are not explicitly set by
> users.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
