Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

NextKeyMarker missing in S3.listObjects response #53

Closed
gramakri opened this Issue Feb 3, 2013 · 5 comments

Comments

Projects
None yet
4 participants
Contributor

gramakri commented Feb 3, 2013

http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/S3/Client.html#listObjects-property should provide a NextKeyMarker property when IsTruncated is true. There is no such property in the result.

Member

trevorrowe commented Feb 4, 2013

The issue appears to be the documentation is incorrect. listObjects will not actually return a netKeyMarker. When the response is truncated, then you will have to grab the key from the last returned contents entry:

nextKeyMarker = data.Contents[data.Contents.length - 1]

I will update the documentation. Lets leave this issue open until the doc changes have been made. Thank you for reporting this issue.

@lsegal lsegal closed this in b2fcfea Feb 4, 2013

Contributor

gramakri commented Feb 7, 2013

nextKeyMarker = data.Contents[data.Contents.length - 1].Key i guess

geuis commented Feb 13, 2014

The documentation still has not been updated, http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/frames.html#!AWS/S3.html. Still says a NextMarker property should be returned, but it is not.

@lsegal lsegal reopened this Feb 13, 2014

Contributor

lsegal commented Feb 13, 2014

The previous fix to this was a manual change to our local docs that were (at the time) hardcoded in the SDK. We've since moved to pulling docs directly from an upstream source, and it looks like the docs have not been fixed there. I will re-open this and make sure this is fixed upstream.

Contributor

lsegal commented May 29, 2014

I am going to close this since the docs have been updated to indicate that NextMarker may not always be present, in which case the last key should be used.

@lsegal lsegal closed this May 29, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment