Skip to content

Commit d1b585d

Browse files
committed
fixed validation warnings
1 parent b2a0a15 commit d1b585d

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ This rowset is now ready for import into Azure Cognitive Search.
107107

108108
On the Azure Cognitive Search side, create an index schema that models the one-to-many relationship using nested JSON. The result set you created in the previous section generally corresponds to the index schema provided below (we cut some fields for brevity).
109109

110-
The following example is similar to the example in [How to model complex data types](search-howto-complex-data-types.md#creating-complex-fields). The *Rooms* structure, which has been the focus of this article, is in the fields collection of an index named *hotels*. This example also shows a complex type for *Address*, which differs from *Rooms* in that it is composed of a fixed set of items, as opposed to the multiple, arbitrary number of items allowed in a collection.
110+
The following example is similar to the example in [How to model complex data types](search-howto-complex-data-types.md#create-complex-fields). The *Rooms* structure, which has been the focus of this article, is in the fields collection of an index named *hotels*. This example also shows a complex type for *Address*, which differs from *Rooms* in that it is composed of a fixed set of items, as opposed to the multiple, arbitrary number of items allowed in a collection.
111111

112112
```json
113113
{

articles/search/search-howto-complex-data-types.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: How to model complex data types
2+
title: Model complex data types
33
titleSuffix: Azure Cognitive Search
44
description: Nested or hierarchical data structures can be modeled in an Azure Cognitive Search index using ComplexType and Collections data types.
55

@@ -8,11 +8,11 @@ author: brjohnstmsft
88
ms.author: brjohnst
99
tags: complex data types; compound data types; aggregate data types
1010
ms.service: cognitive-search
11-
ms.topic: conceptual
11+
ms.topic: how-to
1212
ms.date: 11/17/2021
1313
---
1414

15-
# How to model complex data types in Azure Cognitive Search
15+
# Model complex data types in Azure Cognitive Search
1616

1717
External datasets used to populate an Azure Cognitive Search index can come in many shapes. Sometimes they include hierarchical or nested substructures. Examples might include multiple addresses for a single customer, multiple colors and sizes for a single SKU, multiple authors of a single book, and so on. In modeling terms, you might see these structures referred to as *complex*, *compound*, *composite*, or *aggregate* data types. The term Azure Cognitive Search uses for this concept is **complex type**. In Azure Cognitive Search, complex types are modeled using **complex fields**. A complex field is a field that contains children (sub-fields) which can be of any data type, including other complex types. This works in a similar way as structured data types in a programming language.
1818

0 commit comments

Comments
 (0)