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
+3-6Lines changed: 3 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@ titleSuffix: Azure AI Search
4
4
description: Set up an Azure blob indexer to automate indexing of blob content for full text search operations and knowledge mining in Azure AI Search.
5
5
author: gmndrg
6
6
ms.author: gimondra
7
-
manager: nitinme
7
+
manager: vinodva
8
8
9
9
ms.service: cognitive-search
10
10
ms.custom:
11
11
- ignite-2023
12
12
ms.topic: how-to
13
-
ms.date: 06/25/2024
13
+
ms.date: 08/23/2024
14
14
---
15
15
16
16
# Index data from Azure Blob Storage
@@ -179,7 +179,7 @@ In a [search index](search-what-is-an-index.md), add fields to accept the conten
179
179
180
180
+ A custom metadata property that you add to blobs. This option requires that your blob upload process adds that metadata property to all blobs. Since the key is a required property, any blobs that are missing a value will fail to be indexed. If you use a custom metadata property as a key, avoid making changes to that property. Indexers will add duplicate documents for the same blob if the key property changes.
181
181
182
-
Metadata properties often include characters, such as `/` and `-`, which are invalid for document keys. Because the indexer has a "base64EncodeKeys" property (true by default), it automatically encodes the metadata property, with no configuration or field mapping required.
182
+
Metadata properties often include characters, such as `/` and `-`, which are invalid for document keys. However, the indexer automatically encodes the key metadata property, with no configuration or field mapping required.
183
183
184
184
1. Add a "content" field to store extracted text from each file through the blob's "content" property. You aren't required to use this name, but doing so lets you take advantage of implicit field mappings.
185
185
@@ -203,7 +203,6 @@ Once the index and data source have been created, you're ready to create the ind
203
203
"batchSize": null,
204
204
"maxFailedItems": null,
205
205
"maxFailedItemsPerBatch": null,
206
-
"base64EncodeKeys": null,
207
206
"configuration": {
208
207
"indexedFileNameExtensions" : ".pdf,.docx",
209
208
"excludedFileNameExtensions" : ".png,.jpeg",
@@ -261,7 +260,6 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
261
260
"batchSize": null,
262
261
"maxFailedItems": null,
263
262
"maxFailedItemsPerBatch": null,
264
-
"base64EncodeKeys": null,
265
263
"configuration": {
266
264
"indexedFileNameExtensions" : ".pdf,.docx",
267
265
"excludedFileNameExtensions" : ".png,.jpeg",
@@ -285,7 +283,6 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
0 commit comments