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/vector-search-filters.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ If you don't have source fields with text or numeric values, check for document
45
45
46
46
In the following example, the vector is a representation of this query string: "what Azure services support full text search". The query targets the `contentVector` field. The actual vector has 1,536 embeddings, so it's trimmed for readability.
47
47
48
-
The filter criteria (`category eq 'Databases'`) are applied to a filterable text field (`category`) before the search engine executes the vector query.
48
+
The filter criteria are applied to a filterable text field (`category` in this example) before the search engine executes the vector query.
49
49
50
50
```http
51
51
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
@@ -83,7 +83,7 @@ api-key: {{admin-api-key}}
83
83
84
84
In the following example, the vector is a representation of this query string: "what Azure services support full text search". The query targets the `contentVector` field. The actual vector has 1,536 embeddings, so it's trimmed for readability.
85
85
86
-
The filter criteria (`category eq 'Databases'`) are applied to a filterable text field (`category`) before the search engine executes the vector query.
86
+
The filter criteria are applied to a filterable text field (`category` in this example) before the search engine executes the vector query.
87
87
88
88
```http
89
89
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-05-01-preview
@@ -223,9 +223,7 @@ The following graph shows prefilter relative QPS, computed as prefilter QPS divi
223
223
The vertical axis represents the relative performance of prefiltering compared to postfiltering, expressed as a ratio of QPS (queries per second). For example:
224
224
225
225
+ A value of `0.0` means prefiltering is 100% slower than postfiltering.
226
-
227
226
+ A value of `0.5` means prefiltering is 50% slower.
228
-
229
227
+ A value of `1.0` means prefiltering and post filtering are equivalent.
230
228
231
229
The horizontal axis represents the filtering rate, or the percentage of candidate documents after applying the filter. For example, a rate of `1.00%` means that the filter criteria selected one percent of the search corpus.
0 commit comments