Skip to content

Commit b0aaecb

Browse files
committed
edit
1 parent 870e788 commit b0aaecb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/search/search-relevance-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ In a query operation, the relevance of any given result is measured by a ranking
1717

1818
Ranking occurs whenever the query request includes full text or vector queries. It doesn't occur if the query invokes strict pattern matching, such as a filter-only query or a specialized query form like autocomplete, suggestions, geospatial search, fuzzy search, or regular expression search. A uniform search score of 1.0 indicates the absence of a ranking algorithm.
1919

20-
In Azure AI Search, *relevance tuning* is primarily centered on textual content, applying scoring profiles or semantic ranking to enhance the quality of results. For vectors, you can experiment between Hierarchical Navigable Small World (HNSW) and exhaustive K-nearest neighbors (KNN) to see if one approach outperforms the other. HNSW graphing with an exhaustive KNN override at query time is the most flexible approach for testing. You can also experiment with various embedding models to see which ones produce higher quality results.
20+
In Azure AI Search, *relevance tuning* is primarily centered on textual content, applying scoring profiles or semantic ranking to enhance the quality of results. For vectors, you can experiment between Hierarchical Navigable Small World (HNSW) and exhaustive K-nearest neighbors (KNN) to see if one algorithm outperforms the other for your scenario. HNSW graphing with an exhaustive KNN override at query time is the most flexible approach for testing. You can also experiment with various embedding models to see which ones produce higher quality results.
2121

2222
## Levels of ranking
2323

0 commit comments

Comments
 (0)