s3api ListObjects no NextMarker in result when no Delimiter

Bug #2045912 reported by chenmingjian
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Object Storage (swift)
New
Undecided
chenmingjian

Bug Description

here(https://docs.openstack.org/swift/2023.2/s3_compat.html) I find swift s3 restful api is compatible with s3 ListObjects protocol.

but in s3 page(https://docs.aws.amazon.com/AmazonS3/latest/API/API_ListObjects.html#AmazonS3-ListObjects-response-NextMarker) I find:
NextMarker:
    When the response is truncated (the IsTruncated element value in the response is true), you can use the key name in this field as the marker parameter in the subsequent request to get the next set of objects. Amazon S3 lists objects in alphabetical order.

but no NextMarker in s3api ListObjects results when there is no Delimiter.

Two different performances make s3api loose.

Changed in swift:
assignee: nobody → chenmingjian (chenmingjian)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.