You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-howto-indexing-azure-blob-storage.md
+54-1Lines changed: 54 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.service: cognitive-search
10
10
ms.custom:
11
11
- ignite-2023
12
12
ms.topic: how-to
13
-
ms.date: 05/04/2024
13
+
ms.date: 06/17/2024
14
14
---
15
15
16
16
# 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
243
243
244
244
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).
245
245
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
+
246
299
## Check indexer status
247
300
248
301
To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/get-indexer-status) request:
0 commit comments