Skip to content

Commit c78b801

Browse files
authored
Update search-howto-index-azure-data-lake-storage.md
Removing 'base64EncodeKeys' property which was retired since years ago.
1 parent ce3bdbd commit c78b801

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/search/search-howto-index-azure-data-lake-storage.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ titleSuffix: Azure AI Search
44
description: Set up an Azure Data Lake Storage (ADLS) Gen2 indexer to automate indexing of content and metadata for full text search in Azure AI Search.
55
author: gmndrg
66
ms.author: gimondra
7-
manager: nitinme
7+
manager: vinodva
88
ms.service: cognitive-search
99
ms.custom:
1010
- ignite-2023
1111
ms.topic: how-to
12-
ms.date: 02/19/2024
12+
ms.date: 08/23/2024
1313
---
1414

1515
# Index data from Azure Data Lake Storage Gen2
@@ -166,7 +166,7 @@ In a [search index](search-what-is-an-index.md), add fields to accept the conten
166166

167167
+ 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.
168168

169-
Metadata properties often include characters, such as `/` and `-`, that 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.
169+
Metadata properties often include characters, such as `/` and `-`, that are invalid for document keys. The indexer automatically encodes the key metadata property, with no configuration or field mapping required.
170170

171171
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.
172172

@@ -189,7 +189,6 @@ Once the index and data source have been created, you're ready to create the ind
189189
"batchSize": null,
190190
"maxFailedItems": null,
191191
"maxFailedItemsPerBatch": null,
192-
"base64EncodeKeys": null,
193192
"configuration": {
194193
"indexedFileNameExtensions" : ".pdf,.docx",
195194
"excludedFileNameExtensions" : ".png,.jpeg",

0 commit comments

Comments
 (0)