Skip to content

Commit 3ef9da5

Browse files
authored
Update search-howto-indexing-azure-blob-storage.md
Removing retired property 'base64EncodeKeys' since it doesn't appear in APIs since 2019.
1 parent 8f570c1 commit 3ef9da5

File tree

1 file changed

+3
-6
lines changed

1 file changed

+3
-6
lines changed

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

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,13 @@ titleSuffix: Azure AI Search
44
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.
55
author: gmndrg
66
ms.author: gimondra
7-
manager: nitinme
7+
manager: vinodva
88

99
ms.service: cognitive-search
1010
ms.custom:
1111
- ignite-2023
1212
ms.topic: how-to
13-
ms.date: 06/25/2024
13+
ms.date: 08/23/2024
1414
---
1515

1616
# 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
179179

180180
+ 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.
181181

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.
183183

184184
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.
185185

@@ -203,7 +203,6 @@ Once the index and data source have been created, you're ready to create the ind
203203
"batchSize": null,
204204
"maxFailedItems": null,
205205
"maxFailedItemsPerBatch": null,
206-
"base64EncodeKeys": null,
207206
"configuration": {
208207
"indexedFileNameExtensions" : ".pdf,.docx",
209208
"excludedFileNameExtensions" : ".png,.jpeg",
@@ -261,7 +260,6 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
261260
"batchSize": null,
262261
"maxFailedItems": null,
263262
"maxFailedItemsPerBatch": null,
264-
"base64EncodeKeys": null,
265263
"configuration": {
266264
"indexedFileNameExtensions" : ".pdf,.docx",
267265
"excludedFileNameExtensions" : ".png,.jpeg",
@@ -285,7 +283,6 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
285283
"batchSize": null,
286284
"maxFailedItems": null,
287285
"maxFailedItemsPerBatch": null,
288-
"base64EncodeKeys": null,
289286
"configuration": {
290287
"indexedFileNameExtensions" : ".pdf,.docx",
291288
"excludedFileNameExtensions" : ".png,.jpeg",

0 commit comments

Comments
 (0)