You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To paginate buckets I wanted to make use of the ContinuationToken but NextContinuationToken it isn't contained in the response from S3 although "IsTruncated"="true"
is returned.
NextContinuationToken -> (string)
NextContinuationToken is sent when isTruncated is true, which means there are more keys in the bucket that can be listed. The next list requests to Amazon S3 can be continued with this NextContinuationToken . NextContinuationToken is obfuscated and is not a real key
Am I missing something obvious?
The text was updated successfully, but these errors were encountered:
Okay, I think I now what happens: list_objects_v2 just appends list-type=2 as a query parameter, which will be escaped by _clean_s3_uri to the non-digestable list-type$3D2. So the problem is that the version selector is not working.
317: S3: really call version 2 in `list_objects_v2` r=mattBrzezinski a=laborg
Fixes#316 by only using S3 escape rules for the path.
- With this I can properly use the continuation token for paginated results.
- I don't know enough about minio to know if the added tests are suitable to detect a regression.
- URIs.jl has been added as an dependency, but I feel that this will sooner or later be the case anyway.
Co-authored-by: Gerhard Aigner <gerhard.aigner@gmail.com>
To paginate buckets I wanted to make use of the
ContinuationToken
butNextContinuationToken
it isn't contained in the response from S3 although"IsTruncated"="true"
is returned.
According to https://docs.aws.amazon.com/cli/latest/reference/s3api/list-objects-v2.html
Am I missing something obvious?
The text was updated successfully, but these errors were encountered: