Feature #24493

rgw does not implement list_object_v2 in S3

Added by Yang Yang over 4 years ago. Updated over 3 years ago.

Fix Under Review
Target version:
% Done:


Affected Versions:
Pull request ID:


List_object_v2(get_bucket_v2) is different to list_object in some parameters and returned values.
In most case´╝îit can work well.
But in some special cases,for example, list_object_v2 can not get more than 1000 keys.

So it seems that list_object_v2 is identified as list_object(v1) in rgw.


#1 Updated by Abhishek Lekshmanan over 4 years ago

  • Tracker changed from Bug to Feature
  • Assignee set to Orit Wasserman

#2 Updated by Simon Leinen over 3 years ago

It would be great if rgw fully supported ListObjectsV2. Looking at the spec differences between ListObjects and ListObjectsV2, most of the V2 functionality is already implemented in rgw. In particular, rgw already understands continuation-token, start-after and fetch-owner.

The only thing missing seems to be KeyCount in the v2 response.

Several users of rgw-based storage as the backend for GitLab's container registry have run into this: a maintenance command for cleaning up old container data core dumps because of the missing KeyCount. See Ceph issue 64923. That issue has been worked around upstream in the Docker registry code (docker/distribution issue #2879), but it would be nice if such workarounds wouldn't be necessary.

Implementing the missing KeyCount functionality seems like an achievable goal.

#3 Updated by Albin Antony over 3 years ago

  • Status changed from New to Fix Under Review

rgw supports KeyCount and it is working fine while testing with s3-tests. Could you please let us know if I am missing something?

Also available in: Atom PDF