Skip to content

Commit 51fe828

Browse files
committed
Scrubbed docs for broken links
1 parent 47ca429 commit 51fe828

5 files changed

+3
-269
lines changed

articles/search/TOC.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -258,8 +258,6 @@
258258
href: search-query-understand-collection-filters.md
259259
- name: Filter by language
260260
href: search-filters-language.md
261-
- name: Example of multi-level facets
262-
href: search-example-adventureworks-multilevel-faceting.md
263261
- name: Results
264262
items:
265263
- name: Work with results

articles/search/index-sql-relational-data.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -102,7 +102,7 @@ The solution is to capture the room detail as nested JSON, and then insert the J
102102
This rowset is now ready for import into Azure Cognitive Search.
103103

104104
> [!NOTE]
105-
> This approach assumes that embedded JSON is under the [maximum column size limits of SQL Server](https://docs.microsoft.com/sql/sql-server/maximum-capacity-specifications-for-sql-server). If your data doesn't fit, you can try a programmatic approach, as illustrated in [Example: Model the AdventureWorks Inventory database for Azure Cognitive Search](search-example-adventureworks-modeling.md).
105+
> This approach assumes that embedded JSON is under the [maximum column size limits of SQL Server](https://docs.microsoft.com/sql/sql-server/maximum-capacity-specifications-for-sql-server).
106106

107107
## Use a complex collection for the "many" side of a one-to-many relationship
108108

articles/search/search-example-adventureworks-modeling.md

Lines changed: 0 additions & 161 deletions
This file was deleted.

articles/search/search-example-adventureworks-multilevel-faceting.md

Lines changed: 0 additions & 99 deletions
This file was deleted.

articles/search/search-indexer-field-mappings.md

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,8 @@ Some situations where field mappings are useful:
2424
* You need to Base64 encode or decode your data. Field mappings support several **mapping functions**, including functions for Base64 encoding and decoding.
2525

2626
> [!NOTE]
27-
> The field mapping feature of Azure Cognitive Search indexers provides a simple way to map data fields to index fields, with a few options for data conversion. More complex data might require pre-processing to reshape it into a form that's easy to index.
28-
>
29-
> Microsoft Azure Data Factory is a powerful cloud-based solution for importing and transforming data. You can also write code to transform source data before indexing. For code examples, see [Model relational data](search-example-adventureworks-modeling.md) and [Model multilevel facets](search-example-adventureworks-multilevel-faceting.md).
30-
>
27+
> The field mapping feature of Azure Cognitive Search indexers provides a simple way to map data fields to index fields, with a few options for data conversion. More complex data might require pre-processing to reshape it into a form that's easy to index. One option you might consider is [Azure Data Factory](https://docs.microsoft.com/zure/data-factory/).
28+
3129

3230
## Set up field mappings
3331

@@ -242,8 +240,6 @@ Azure SQL Database doesn't have a built-in data type that naturally maps to `Col
242240
}]
243241
```
244242

245-
For a detailed example that transforms relational data into index collection fields, see [Model relational data](search-example-adventureworks-modeling.md).
246-
247243
<a name="urlEncodeFunction"></a>
248244

249245
### urlEncode function

0 commit comments

Comments
 (0)