[
https://issues.apache.org/jira/browse/HDDS-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669971#comment-16669971
]
Elek, Marton commented on HDDS-659:
-----------------------------------
Tested and worked well
1. full robot tests are passed
2. Tested with aws cli
Not sure about the problem with max-items/max-keys. For me it seems to be
working:
I tested with aws s3api (and not aws s3) and worked well.
As an example:
{code}
aws s3api --endpoint-url http://localhost:9878 list-objects-v2 --bucket=blist
--max-items=0
--starting-token=eyJDb250aW51YXRpb25Ub2tlbiI6IG51bGwsICJib3RvX3RydW5jYXRlX2Ftb3VudCI6IDJ9
{code}
Everything looks good to me. Will commit it soom.
> Implement pagination in GET bucket (object list) endpoint
> ---------------------------------------------------------
>
> Key: HDDS-659
> URL: https://issues.apache.org/jira/browse/HDDS-659
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Elek, Marton
> Assignee: Bharat Viswanadham
> Priority: Blocker
> Attachments: HDDS-659.00-WIP.patch, HDDS-659.01.patch,
> HDDS-659.02.patch, HDDS-659.03.patch
>
>
> The current implementation always returns with all the elements. We need to
> support paging with supporting the following headers:
> * {{start-after}}
> * {{continuation-token}}{{}}
> * {{max-keys}}{{}}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
