[
https://issues.apache.org/jira/browse/HDFS-11569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15958657#comment-15958657
]
Weiwei Yang commented on HDFS-11569:
------------------------------------
Further I am thinking how we handle the {{maxNumOfKeys}}, what if number of
available keys exceeds this count? E.g if user request for all keys with prefix
"somekey", by looking up KSM, there is 1500 keys have this prefix, then we
return client 1000 keys and set {{truncated}} to true in {{ListKeys}}? How
client retrieves the rest 500 keys?
It looks like we still want pagination in client side, lets say make
{{ListKeys}} class enumerable, just like s3 API
[http://docs.aws.amazon.com/AmazonS3/latest/dev/ListingObjectKeysUsingJava.html].
That can be done in a separate jira when we work on the implementation of
{{DistributedStorageHandler#listKeys}}. What do you think?
> Ozone: Implement listKey function for KeyManager
> ------------------------------------------------
>
> Key: HDFS-11569
> URL: https://issues.apache.org/jira/browse/HDFS-11569
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Attachments: HDFS-11569-HDFS-7240.001.patch,
> HDFS-11569-HDFS-7240.002.patch, HDFS-11569-HDFS-7240.003.patch,
> HDFS-11569-HDFS-7240.004.patch, HDFS-11569-HDFS-7240.005.patch
>
>
> List keys by prefix from a container. This will need to support pagination
> for the purpose of small object support. So the listKey function returns
> something like ListKeyResult, client can iterate the object to get pagination
> results.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
