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/hybrid-search-how-to-query.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ The following example shows a hybrid query request using the REST API.
105
105
This example is from the [vector quickstart](https://raw.githubusercontent.com/Azure-Samples/azure-search-rest-samples/refs/heads/main/Quickstart-vectors/az-search-quickstart-vectors.rest) that has vector and nonvector content, and several query examples. For brevity, the vector is truncated in this article.
106
106
107
107
```http
108
-
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
108
+
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
109
109
Content-Type: application/json
110
110
api-key: {{admin-api-key}}
111
111
{
@@ -240,7 +240,7 @@ This section has multiple query examples that illustrate hybrid query patterns.
240
240
This example adds a filter, which is applied to the `filterable` nonvector fields of the search index.
241
241
242
242
```http
243
-
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
243
+
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
244
244
Content-Type: application/json
245
245
api-key: {{admin-api-key}}
246
246
{
@@ -324,7 +324,7 @@ Assuming that you [have semantic ranker](semantic-how-to-enable-disable.md) and
324
324
Whenever you use semantic ranking with vectors, make sure `k` is set to 50. Semantic ranker uses up to 50 matches as input. Specifying less than 50 deprives the semantic ranking models of necessary inputs.
325
325
326
326
```http
327
-
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
327
+
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
328
328
Content-Type: application/json
329
329
api-key: {{admin-api-key}}
330
330
{
@@ -365,7 +365,7 @@ api-key: {{admin-api-key}}
365
365
Here's the last query in the collection. It's the same semantic hybrid query as the previous example, but with a filter.
366
366
367
367
```http
368
-
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
368
+
POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
Copy file name to clipboardExpand all lines: articles/search/index-add-scoring-profiles.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,7 +77,7 @@ The following definition shows a simple profile named "geo". This example boosts
77
77
To use this scoring profile, your query is formulated to specify `scoringProfile` parameter in the request. If you're using the REST API, queries are specified through GET and POST requests. In the following example, "currentLocation" has a delimiter of a single dash (`-`). It's followed by longitude and latitude coordinates, where longitude is a negative value.
78
78
79
79
```http
80
-
POST /indexes/hotels/docs&api-version=2024-07-01
80
+
POST /indexes/hotels/docs&api-version=@search.rerankerBoostedScore
Copy file name to clipboardExpand all lines: articles/search/index-add-suggesters.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -161,7 +161,7 @@ In a search application, client code should use a library like [jQuery UI Autoco
161
161
API usage is illustrated in the following call to the Autocomplete REST API. There are two takeaways from this example. First, as with all queries, the operation is against the documents collection of an index and the query includes a `search` parameter, which in this case provides the partial query. Second, you must add `suggesterName` to the request. If a suggester isn't defined in the index, calls to autocomplete or suggestions fail.
162
162
163
163
```http
164
-
POST /indexes/myxboxgames/docs/autocomplete?search&api-version=2024-07-01
164
+
POST /indexes/myxboxgames/docs/autocomplete?search&api-version=@search.rerankerBoostedScore
@@ -84,7 +84,7 @@ The following links describe the Similarity property in the Azure SDKs.
84
84
You can also use the [REST API](/rest/api/searchservice/indexes/create). The following example creates a new index with the "similarity" property set to BM25:
85
85
86
86
```http
87
-
PUT [service-name].search.windows.net/indexes/[index name]?api-version=2024-07-01
87
+
PUT [service-name].search.windows.net/indexes/[index name]?api-version=@search.rerankerBoostedScore
Copy file name to clipboardExpand all lines: articles/search/index-similarity-and-scoring.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@ By default, the score of a document is calculated based on statistical propertie
97
97
If you prefer to compute the score based on the statistical properties across all shards, you can do so by adding `scoringStatistics=global` as a [query parameter](/rest/api/searchservice/documents/search-post) (or add `"scoringStatistics": "global"` as a body parameter of the [query request](/rest/api/searchservice/documents/search-post)).
98
98
99
99
```http
100
-
POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=2024-07-01
100
+
POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=@search.rerankerBoostedScore
101
101
{
102
102
"search": "<query string>",
103
103
"scoringStatistics": "global"
@@ -107,7 +107,7 @@ POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-ve
107
107
Using `scoringStatistics` will ensure that all shards in the same replica provide the same results. That said, different replicas can be slightly different from one another as they're always getting updated with the latest changes to your index. In some scenarios, you might want your users to get more consistent results during a "query session". In such scenarios, you can provide a `sessionId` as part of your queries. The `sessionId` is a unique string that you create to refer to a unique user session.
108
108
109
109
```http
110
-
POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=2024-07-01
110
+
POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=@search.rerankerBoostedScore
Copy file name to clipboardExpand all lines: articles/search/monitor-azure-cognitive-search-data-reference.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,7 +160,7 @@ The following example illustrates a resource log that includes common properties
160
160
| Resource | String | Resource ID. For example: `/subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group-name>/providers/Microsoft.Search/searchServices/<your-search-service-name>`|
161
161
| Category | String | "OperationLogs". This value is a constant. OperationLogs is the only category used for resource logs. |
162
162
| OperationName | String | The name of the operation (see the [full list of operations](#resource-log-search-ops)). An example is `Query.Search`|
163
-
| OperationVersion | String | The api-version used on the request. For example: `2024-07-01`|
163
+
| OperationVersion | String | The api-version used on the request. For example: `@search.rerankerBoostedScore`|
164
164
| ResultType | String |"Success". Other possible values: Success or Failure |
165
165
| ResultSignature | Int | An HTTP result code. For example: `200`|
166
166
| DurationMS | Int | Duration of the operation in milliseconds. |
@@ -177,7 +177,7 @@ The following properties are specific to Azure AI Search.
177
177
| Description_s | String | The operation's endpoint. For example: `GET /indexes('content')/docs`|
178
178
| Documents_d | Int | Number of documents processed. |
179
179
| IndexName_s | String | Name of the index associated with the operation. |
180
-
| Query_s | String | The query parameters used in the request. For example: `?search=beach access&$count=true&api-version=2024-07-01`|
180
+
| Query_s | String | The query parameters used in the request. For example: `?search=beach access&$count=true&api-version=@search.rerankerBoostedScore`|
Copy file name to clipboardExpand all lines: articles/search/query-lucene-syntax.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ To use full Lucene syntax, set the queryType to `full` and pass in a query expre
24
24
The following example is a search request constructed using the full syntax. This particular example shows in-field search and term boosting. It looks for hotels where the category field contains the term `budget`. Any documents containing the phrase `"recently renovated"` are ranked higher as a result of the term boost value (3).
25
25
26
26
```http
27
-
POST /indexes/hotels-sample-index/docs/search?api-version=2024-07-01
27
+
POST /indexes/hotels-sample-index/docs/search?api-version=@search.rerankerBoostedScore
28
28
{
29
29
"queryType": "full",
30
30
"search": "category:budget AND \"recently renovated\"^3",
0 commit comments