<p>Found the spot to hack this. It was not within the <code>AssetIndexTool</code> as originally theorized, but in the  In <code>RackspaceAssetSourceType</code> in the <code>_getFileList</code> function you can append a <code>marker</code> <code>marker_end</code> and/or <code>limit</code> to the file list.</p>

<p>The <code>marker</code> should just be a URI without the extension. As an example, we change the parameters on <code>$targetUri</code> to look like so:</p>

<p><code>&amp;format=json&amp;marker=products/BC-174&amp;limit=250';</code></p>

<p>This will index the items form that marker and effectively ignore all the other assets you have already indexed. Craft will prompt you to delete the items you already have, as they are not found because you have skipped them by hacking the <code>$fileList</code>.</p>

<p>I've found you can safely hit <em>Cancel</em> and your items from the marker range will be imported, and your other indexes will not be affected.</p>

<p><a href="https://developer.rackspace.com/docs/cloud-files/v1/storage-api-reference/container-services-operations/#show-container-details-and-list-objects" rel="nofollow noreferrer">This article</a> is very helpful in finding out what you can do with the <code>marker</code> params. </p>

CC BY-SA 3.0
2017-08-10T22:05:20.240Z
2017-08-10T22:05:20.240Z
Ian
<p>Original question from Craft Slack:</p>

<p>Is there anyway to hack the <code>AssetIndexTool</code> to start at a certain asset/position/filename/index?</p>

<p>We’re using Rackspace Cloud Files and have around 25k images loaded. However, Cloud Files is limited to returning 10,000 objects per “page”. And it doesn’t look like Craft will paginate these objects. Wondering if we can just hack it to start the asset indexing at a certain place instead of starting at a certain index/filename, etc.</p>

<assets>
Overcoming Rackspace Cloud Files 10,000 object limit
# Overcoming Rackspace Cloud Files 10,000 object limit

(Asked by: username_0 on 2017-08-10)

Original question from Craft Slack:

Is there anyway to hack the `AssetIndexTool` to start at a certain asset/position/filename/index?

We’re using Rackspace Cloud Files and have around 25k images loaded. However, Cloud Files is limited to returning 10,000 objects per “page”. And it doesn’t look like Craft will paginate these objects. Wondering if we can just hack it to start the asset indexing at a certain place instead of starting at a certain index/filename, etc.

**Tags:** assets

---

## 1 answers

### Answer by username_0 on 2017-08-10. Score: 2

Found the spot to hack this. It was not within the `AssetIndexTool` as originally theorized, but in the In `RackspaceAssetSourceType` in the `_getFileList` function you can append a `marker` `marker_end` and/or `limit` to the file list.

The `marker` should just be a URI without the extension. As an example, we change the parameters on `$targetUri` to look like so:

`&format=json▮=products/BC-174&limit=250';`

This will index the items form that marker and effectively ignore all the other assets you have already indexed. Craft will prompt you to delete the items you already have, as they are not found because you have skipped them by hacking the `$fileList`.

I've found you can safely hit *Cancel* and your items from the marker range will be imported, and your other indexes will not be affected.

[This article](https://developer.rackspace.com/docs/cloud-files/v1/storage-api-reference/container-services-operations/#show-container-details-and-list-objects) is very helpful in finding out what you can do with the `marker` params.


---

