[
https://issues.apache.org/jira/browse/JCLOUDS-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14013138#comment-14013138
]
rahul ruikar commented on JCLOUDS-577:
--------------------------------------
As per open stack docs, there should be multiple requests if records are more
than 10000, ( with setting marker,limit and end_marker)
Does jcloud-cli allows to set marker,limit,end_market options.. ???
There are 3 variants of API, 2 of them doesnt take care of records more than
10000.
1. this also has TODO
114 public PageSet<? extends StorageMetadata> list() {
115 // TODO: there may eventually be >10k containers.
2. with no options...marker , limit , etc...
147 public PageSet<? extends StorageMetadata> list(String container) {
148 return list(container, ListContainerOptions.NONE);
149 }
3. this API set's marker, limit, en_marker options if provided..
152 public PageSet<? extends StorageMetadata> list(final String container,
ListContainerOptions options) {
I am not sure whether jclouds-cli allows these parameters in command... I will
deep dig if someone confirms this..
but there has to be multiple requests to get more than 10000 records..
> jclouds-cli blobstore container-list only lists the first 10K containers
> ------------------------------------------------------------------------
>
> Key: JCLOUDS-577
> URL: https://issues.apache.org/jira/browse/JCLOUDS-577
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-cli
> Affects Versions: 1.6.0
> Reporter: Shri Javadekar
>
> I used jclouds-cli to get a list of containers that we have on RackSpace
> cloudfiles-us. This result only returned 10K containers. When I tried this
> using the swift command line tool, it showed me that there were 10749
> containers.
> I verified found that some of the more recently created containers were not
> returned by the contianer-list command.
> However, if we already know the name of the container, other commands such as
> list (list blobs in the container), container-exists, etc. worked correctly.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
