[
https://issues.apache.org/jira/browse/HDFS-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16073643#comment-16073643
]
Weiwei Yang commented on HDFS-12083:
------------------------------------
Hi [~nandakumar131]
Thanks for filing this. I agree. From pagination point of view, it is easier to
use prev-key in the listing result, for example we have keys
{noformat}a, b, c, d, e{noformat}
so to get multi-page result, we can use following calls
{code}
listKeys -> prev-key=null, max-keys=2 -> a, b
listKeys -> prev-key=b, max-keys=2 -> c, d
listKeys -> prev-key=d, max-keys=2 -> e
{code}
when you work on this, please also keep our java doc (for listing methods) and
documentation ({{OzoneRest.md}}) up-to-date.
Thanks a lot!
> Ozone: KSM: previous key has to be excluded from result in listVolumes,
> listBuckets and listKeys
> ------------------------------------------------------------------------------------------------
>
> Key: HDFS-12083
> URL: https://issues.apache.org/jira/browse/HDFS-12083
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Nandakumar
> Assignee: Nandakumar
>
> When previous key is set as part of list calls [listVolume, listBuckets &
> listKeys], the result includes previous key, there is no need to have this in
> the result.
> Since previous key is present as part of result, we will never receive an
> empty list in the subsequent list calls, this makes it difficult to have a
> exit criteria where we want to get all the values using multiple list calls
> (with previous-key set).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
