Following on from https://github.com/aquarist-labs/ceph/pull/39, we should implement a class that knows how to iterate through metadata keys (users, buckets, ... what else?) so that the max and truncated arguments to SFStore::meta_list_keys_next() will actually work. Note in particular that when listing buckets via the admin REST API, that code tries to iterate through buckets 1000 at a time. Our current implementation of SFStore::meta_list_keys_next() will just return everything, because it can't handle max and truncated.
Following on from https://github.com/aquarist-labs/ceph/pull/39, we should implement a class that knows how to iterate through metadata keys (users, buckets, ... what else?) so that the
max
andtruncated
arguments toSFStore::meta_list_keys_next()
will actually work. Note in particular that when listing buckets via the admin REST API, that code tries to iterate through buckets 1000 at a time. Our current implementation ofSFStore::meta_list_keys_next()
will just return everything, because it can't handlemax
andtruncated
.