Skip to content

Commit f320748

Browse files
committed
fixed a bookmark error
1 parent 3b16dd2 commit f320748

File tree

2 files changed

+20
-2
lines changed

2 files changed

+20
-2
lines changed

articles/search/search-file-storage-integration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ A primary difference between a file share indexer and other indexers is the data
4848
}
4949
```
5050

51-
1. Set "type" to "azurefile" (required).
51+
1. Set "type" to `"azurefile"` (required).
5252

5353
1. Set "credentials" to an Azure Storage connection string. The next section describes the supported formats.
5454

@@ -118,7 +118,7 @@ In the [search index](search-what-is-an-index.md), add fields to accept the cont
118118
+ **metadata_storage_last_modified** (`Edm.DateTimeOffset`) - last modified timestamp for the file. Azure Cognitive Search uses this timestamp to identify changed files, to avoid reindexing everything after the initial indexing.
119119
+ **metadata_storage_size** (`Edm.Int64`) - file size in bytes.
120120
+ **metadata_storage_content_md5** (`Edm.String`) - MD5 hash of the file content, if available.
121-
+ **metadata_storage_sas_token** (`Edm.String`) - A temporary SAS token that can be used by [custom skills](cognitive-search-custom-skill-interface.md) to get access to the file. This token shouldn't stored for later use as it might expire.
121+
+ **metadata_storage_sas_token** (`Edm.String`) - A temporary SAS token that can be used by [custom skills](cognitive-search-custom-skill-interface.md) to get access to the file. This token shouldn't be stored for later use as it might expire.
122122

123123
## Configure the file indexer
124124

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

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -266,6 +266,24 @@ Lastly, any metadata properties specific to the document format of the blobs you
266266

267267
It's important to point out that you don't need to define fields for all of the above properties in your search index - just capture the properties you need for your application.
268268

269+
## How to control which blobs are indexed
270+
271+
You can control which blobs are indexed, and which are skipped, by the blob's file type or by setting properties on the blob themselves, causing the indexer to skip over them.
272+
273+
Include specific file extensions by setting `"indexedFileNameExtensions"` to a comma-separated list of file extensions (with a leading dot). Exclude specific file extensions by setting `"excludedFileNameExtensions"` to the extensions that should be skipped. If the same extension is in both lists, it will be excluded from indexing.
274+
275+
```http
276+
PUT /indexers/[indexer name]?api-version=2020-06-30
277+
{
278+
"parameters" : {
279+
"configuration" : {
280+
"indexedFileNameExtensions" : ".pdf, .docx",
281+
"excludedFileNameExtensions" : ".png, .jpeg"
282+
}
283+
}
284+
}
285+
```
286+
269287
## How blobs are indexed
270288

271289
By default, most blobs are indexed as a single search document in the index, including blobs with structured content, such as JSON or CSV, which are indexed as a single chunk of text. However, for JSON or CSV documents that have an internal structure (delimiters), you can assign parsing modes to generate individual search documents for each line or element:

0 commit comments

Comments
 (0)