Opened on Jun 25, 2011 at 3:59:05 PM
Closed on Jun 26, 2011 at 11:13:18 AM
Last modified on Jun 26, 2011 at 2:38:10 PM
#6037 closed defect (fixed)
Rackspace CloudFiles 10000 Container/Folder Limit in Cyberduck
Reported by: | samsen | Owned by: | dkocher |
---|---|---|---|
Priority: | high | Milestone: | 4.1 |
Component: | cloudfiles | Version: | 4.0.2 |
Severity: | major | Keywords: | Marker |
Cc: | Architecture: | Intel | |
Platform: | Windows 7 |
Description (last modified by dkocher)
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...
Change History (5)
comment:1 Changed on Jun 25, 2011 at 4:18:16 PM by samsen
comment:2 Changed on Jun 26, 2011 at 11:11:39 AM by dkocher
- Description modified (diff)
comment:3 Changed on Jun 26, 2011 at 11:12:27 AM by dkocher
The previous tickets talked about the listing of files within containers.
comment:4 Changed on Jun 26, 2011 at 11:13:18 AM by dkocher
- Resolution set to fixed
- Status changed from new to closed
In r8836.
comment:5 Changed on Jun 26, 2011 at 2:38:10 PM by samsen
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.
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