Skip to content

Commit 277dae1

Browse files
authored
Update search-howto-indexing-azure-blob-storage.md
Updated with example of how to index data from multiple containers.
1 parent 3075345 commit 277dae1

File tree

1 file changed

+54
-1
lines changed

1 file changed

+54
-1
lines changed

articles/search/search-howto-indexing-azure-blob-storage.md

Lines changed: 54 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: cognitive-search
1010
ms.custom:
1111
- ignite-2023
1212
ms.topic: how-to
13-
ms.date: 05/04/2024
13+
ms.date: 06/17/2024
1414
---
1515

1616
# Index data from Azure Blob Storage
@@ -243,6 +243,59 @@ Once the index and data source have been created, you're ready to create the ind
243243

244244
An indexer runs automatically when it's created. You can prevent this by setting "disabled" to true. To control indexer execution, [run an indexer on demand](search-howto-run-reset-indexers.md) or [put it on a schedule](search-howto-schedule-indexers.md).
245245

246+
## Indexing data from multiple Azure Blob containers to a single index
247+
248+
Keep in mind that an indexer can only index data from a single container. If your requirement is to index data from multiple containers and consolidate it into a single AI Search index, this can be achieved by configuring multiple indexers, all directed to the same index. Please be aware of the [maximum number of indexers available per SKU](search-limits-quotas-capacity.md#indexer-limits).
249+
250+
To illustrate, let's consider an example of two indexers, pulling data from two distinct data sources, named `my-blob-datasource1` and `my-blob-datasource2`. Each data source points to a separate Azure Blob container, but both direct to the same index named `my-search-index`:
251+
252+
```http
253+
POST https://[service name].search.windows.net/indexers?api-version=2023-11-01
254+
{
255+
"name" : "my-blob-indexer1",
256+
"dataSourceName" : "my-blob-datasource1",
257+
"targetIndexName" : "my-search-index",
258+
"parameters": {
259+
"batchSize": null,
260+
"maxFailedItems": null,
261+
"maxFailedItemsPerBatch": null,
262+
"base64EncodeKeys": null,
263+
"configuration": {
264+
"indexedFileNameExtensions" : ".pdf,.docx",
265+
"excludedFileNameExtensions" : ".png,.jpeg",
266+
"dataToExtract": "contentAndMetadata",
267+
"parsingMode": "default"
268+
}
269+
},
270+
"schedule" : { },
271+
"fieldMappings" : [ ]
272+
}
273+
```
274+
275+
276+
```http
277+
POST https://[service name].search.windows.net/indexers?api-version=2023-11-01
278+
{
279+
"name" : "my-blob-indexer2",
280+
"dataSourceName" : "my-blob-datasource2",
281+
"targetIndexName" : "my-search-index",
282+
"parameters": {
283+
"batchSize": null,
284+
"maxFailedItems": null,
285+
"maxFailedItemsPerBatch": null,
286+
"base64EncodeKeys": null,
287+
"configuration": {
288+
"indexedFileNameExtensions" : ".pdf,.docx",
289+
"excludedFileNameExtensions" : ".png,.jpeg",
290+
"dataToExtract": "contentAndMetadata",
291+
"parsingMode": "default"
292+
}
293+
},
294+
"schedule" : { },
295+
"fieldMappings" : [ ]
296+
}
297+
```
298+
246299
## Check indexer status
247300

248301
To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/get-indexer-status) request:

0 commit comments

Comments
 (0)