You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/search/search-how-to-define-index-projections.md
+5-3Lines changed: 5 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ Indexers load indexed data into a predefined index. How you define the schema an
52
52
53
53
## Create an index for one-to-many indexing
54
54
55
-
Whether you create one index for chunks that repeats parent values, or separate indexes for parent-child field placement, the primary index used for searching is designed around data chunks. It must have the following fields:
55
+
Whether you create one index for chunks that repeat parent values, or separate indexes for parent-child field placement, the primary index used for searching is designed around data chunks. It must have the following fields:
56
56
57
57
- A document key field uniquely identifying each document. It must be defined as type `Edm.String` with the `keyword` analyzer.
58
58
@@ -140,7 +140,7 @@ This example is similar to the [RAG tutorial](tutorial-rag-build-solution-index-
140
140
141
141
## Add index projections to a skillset
142
142
143
-
Index projections are defined inside a skillset definition and are primarily defined as an array of `selectors`, where each selector corresponds to a different target index on the search service. This section describes each parameter and includes [steps and examples](#how-to-specify-an-index-projections-definition) for setting up the projections.
143
+
Index projections are defined inside a skillset definition and are primarily defined as an array of `selectors`, where each selector corresponds to a different target index on the search service. This section describes each parameter and includes [steps and examples](#how-to-specify-an-indexprojections-definition) for setting up the projections.
144
144
145
145
### Parameter reference
146
146
@@ -166,7 +166,7 @@ This requirement is in contrast with other field mapping conventions in Azure AI
166
166
167
167
### How to specify an `indexProjections` definition
168
168
169
-
Choose the tab for the API syntax. There's currently no portal support for setting up projections, other than editing the skillset JSON definition.
169
+
Choose a tab for the various API syntax. There's currently no portal support for setting up projections, other than editing the skillset JSON definition. Refer to the REST example for JSON.
0 commit comments