Skip to content

Commit 1df100b

Browse files
authored
Update vector-search-how-to-assign-narrow-data-types.md
Acrolinx
1 parent 70b8838 commit 1df100b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/search/vector-search-how-to-assign-narrow-data-types.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Data types are assigned to fields in an index definition. You can use the Azure
2020

2121
- An embedding model that output small data formats.
2222

23-
## Suppported narrow data types
23+
## Supported narrow data types
2424

2525
1. Review the [data types used for vector fields](/rest/api/searchservice/supported-data-types#edm-data-types-for-vector-fields) for recommended usage:
2626

@@ -49,7 +49,7 @@ Data types are assigned to fields in an index definition. You can use the Azure
4949

5050
[Define and build the index](vector-search-how-to-create-index.md). You can use the Azure portal, [Create or Update Index (REST API)](/rest/api/searchservice/indexes/create-or-update), or an Azure SDK package for this step.
5151

52-
This field definition uses a narrow data type, `Collection(Edm.Half)`, that can accept a float32 embedding stored as as float16 value. As is true for all vector fields, `dimensions` and `vectorSearchProfile` are set. The specifics of the `vectorSearchProfile` are immaterial to the datatype.
52+
This field definition uses a narrow data type, `Collection(Edm.Half)`, that can accept a float32 embedding stored as a float16 value. As is true for all vector fields, `dimensions` and `vectorSearchProfile` are set. The specifics of the `vectorSearchProfile` are immaterial to the datatype.
5353

5454
We recommend that you set `retrievable` and `stored` to true if you want to visually check the values of the field. On a subsequent rebuild, you can change these properties to false for reduced storage requirements.
5555

0 commit comments

Comments
 (0)