Skip to content

Commit 4040de2

Browse files
committed
Updated vector content
1 parent 5844021 commit 4040de2

File tree

2 files changed

+9
-9
lines changed

2 files changed

+9
-9
lines changed

articles/search/vector-search-how-to-create-index.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -97,14 +97,14 @@ A vector configuration includes:
9797

9898
### [**2024-07-01**](#tab/config-2024-07-01)
9999

100-
[**2024-07-01**](/rest/api/searchservice/search-service-api-versions#2024-07-01) is generally available. It supports a vector configuration having:
101-
102-
+ Hierarchical navigable small world (HNSW) algorithm
103-
+ Exhaustive k-nearest neighbor (KNN) algorithm
104-
+ Scalar compression
105-
+ Binary compression (available in 2024-07-01 only and in newer Azure SDK packages)
106-
+ Oversampling
107-
+ Reranking with original vectors
100+
[**2024-07-01**](/rest/api/searchservice/search-service-api-versions#2024-07-01) is generally available. It supports a vector configuration that has:
101+
102+
+ The hierarchical navigable small world (HNSW) algorithm.
103+
+ The exhaustive k-nearest neighbor (KNN) algorithm.
104+
+ Scalar compression.
105+
+ Binary compression, which is available in 2024-07-01 only and in newer Azure SDK packages.
106+
+ Oversampling.
107+
+ Reranking with original vectors.
108108

109109
If you choose HNSW on a field, you can opt for exhaustive KNN at query time. However, the opposite doesn’t work. If you choose exhaustive for indexing, you can’t later request HNSW search because the extra data structures that enable approximate search don’t exist.
110110

articles/search/vector-search-how-to-query.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ You can also use [Search Explorer](search-explorer.md) in the Azure portal.
3939

4040
## Convert a query string input into a vector
4141

42-
To query a vector field, the query itself must be a vector.
42+
To query a vector field, the query itself must be a vector.
4343

4444
One approach for converting a user's text query string into its vector representation is to call an embedding library or API in your application code. As a best practice, *always use the same embedding models used to generate embeddings in the source documents*. You can find code samples showing [how to generate embeddings](vector-search-how-to-generate-embeddings.md) in the [azure-search-vector-samples](https://github.com/Azure/azure-search-vector-samples) repo.
4545

0 commit comments

Comments
 (0)