Skip to content
New issue

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

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rackspace CloudFiles 10000 Container/Folder Limit in Cyberduck #6037

Closed
cyberduck opened this issue Jun 25, 2011 · 4 comments
Closed

Rackspace CloudFiles 10000 Container/Folder Limit in Cyberduck #6037

cyberduck opened this issue Jun 25, 2011 · 4 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jun 25, 2011

a998853 created the issue

There are repeated messages, saying that this has been fixed, but it appears that this is not the case.

We continue to see only 10,000 containers when we have over 12,000 containers in our CloudFiles Account.

We are running Cyberduck 4.02 8601

And we might be able to live with this if searches extended beyond the 10,000 containers, but it appears that the searches only take place within the first 10,000 containers found...

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 25, 2011

a998853 commented

The system will return a [maximum] of 10,000 container names per request. To retrieve
subsequent container names, another request must be made with a 'marker' parameter.
The marker indicates where the last list left off; the system will return container names
greater than this marker, up to 10,000 again. Note that the ‘marker’ value should be URLencoded prior to sending the HTTP request.

If 10,000 is larger than desired, a 'limit' parameter may be given.

If the number of container names returned equals the limit given (or 10,000 if no limit is
given), it can be assumed there are more container names to be listed. If the container
name list is exactly divisible by the limit, the last request will simply have no content.

Example 4.8. List Large Number of Containers

For example, let's use a listing of five container names
apples
bananas
kiwis
oranges
pears

We'll use a limit of two to show how things work:
GET //?limit=2
Host: storage.clouddrive.com
X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbbCloud Files™ Developer Guide May 24, 2011 API v1
14
apples
bananas

Since we received two items back, we can assume there are more container names to list,
so we make another request with a marker of the last item returned:
GET //?limit=2&marker=bananas
Host: storage.clouddrive.com
X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb

kiwis
oranges
Again, two items are returned; there may be more:
GET //?limit=2&marker=oranges
Host: storage.clouddrive.com
X-Auth-Token: eaaafd18-0fed-4b3a-81b4-663c99ec1cbb
pears

With this one-item response we received less than the limit number of container names,
indicating that this is the end of the list

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 26, 2011

@dkocher commented

The previous tickets talked about the listing of files within containers.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 26, 2011

@dkocher commented

In 995da5a.

Loading

@cyberduck cyberduck closed this Jun 26, 2011
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jun 26, 2011

a998853 commented

Yes, I was fixated on the 10,000 number that must apply to both containers AND the content of containers, so that I didn't distinguish them. So thank-you for fixing the issue.

Loading

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants