Skip to content

Commit 9edbddb

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #7334 from HeidiSteen/heidist-0901
Bulk API version change
2 parents 957e75c + c2d4843 commit 9edbddb

10 files changed

+30
-30
lines changed

‎articles/search/search-how-to-load-search-index.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ In the Azure portal, use an [import wizard](search-import-data-portal.md) to cre
5757
1. Formulate a POST call specifying the index name, the "docs/index" endpoint, and a request body that includes the `@search.action` parameter.
5858

5959
```http
60-
POST https://[service name].search.windows.net/indexes/hotels-sample-index/docs/index?api-version=2024-07-01
60+
POST https://[service name].search.windows.net/indexes/hotels-sample-index/docs/index?api-version=@search.rerankerBoostedScore
6161
Content-Type: application/json
6262
api-key: [admin key]
6363
{
@@ -95,7 +95,7 @@ In the Azure portal, use an [import wizard](search-import-data-portal.md) to cre
9595
1. [Look up the documents](/rest/api/searchservice/documents/get) you just added as a validation step:
9696
9797
```http
98-
GET https://[service name].search.windows.net/indexes/hotel-sample-index/docs/1111?api-version=2024-07-01
98+
GET https://[service name].search.windows.net/indexes/hotel-sample-index/docs/1111?api-version=@search.rerankerBoostedScore
9999
```
100100
101101
When the document key or ID is new, **null** becomes the value for any field that is unspecified in the document. For actions on an existing document, updated values replace the previous values. Any fields that weren't specified in a "merge" or "mergeUpload" are left intact in the search index.

‎articles/search/search-howto-index-azure-data-lake-storage.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -232,7 +232,7 @@ An indexer runs automatically when it's created. You can prevent this by setting
232232
To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/indexers/get-status) request:
233233

234234
```http
235-
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
235+
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=@search.rerankerBoostedScore
236236
Content-Type: application/json
237237
api-key: [admin key]
238238
```
@@ -284,7 +284,7 @@ By default, the blob indexer stops as soon as it encounters a blob with an unsup
284284
There are five indexer properties that control the indexer's response when errors occur.
285285

286286
```http
287-
PUT /indexers/[indexer name]?api-version=2024-07-01
287+
PUT /indexers/[indexer name]?api-version=@search.rerankerBoostedScore
288288
{
289289
"parameters" : {
290290
"maxFailedItems" : 10,

‎articles/search/search-howto-index-changed-deleted-blobs.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ In Azure AI Search, set a native blob soft deletion detection policy on the data
7878
Set the soft deletion detection policy in the data source definition. Specify the API version when creating or updating the data source.
7979

8080
```http
81-
PUT https://[service name].search.windows.net/datasources/blob-datasource?api-version=2024-07-01
81+
PUT https://[service name].search.windows.net/datasources/blob-datasource?api-version=@search.rerankerBoostedScore
8282
Content-Type: application/json
8383
api-key: [admin key]
8484
{
@@ -117,7 +117,7 @@ There are steps to follow in both Azure Storage and Azure AI Search, but there a
117117
1. In Azure AI Search, edit the data source definition to include a "dataDeletionDetectionPolicy" property. For example, the following policy considers a file to be deleted if it has a metadata property `IsDeleted` with the value `true`:
118118

119119
```http
120-
PUT https://[service name].search.windows.net/datasources/file-datasource?api-version=2024-07-01
120+
PUT https://[service name].search.windows.net/datasources/file-datasource?api-version=@search.rerankerBoostedScore
121121
{
122122
"name" : "file-datasource",
123123
"type" : "azurefile",

‎articles/search/search-howto-index-cosmosdb.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ The data source definition specifies the data to index, credentials, and policie
104104
1. [Create or update a data source](/rest/api/searchservice/data-sources/create-or-update) to set its definition:
105105

106106
```http
107-
POST https://[service name].search.windows.net/datasources?api-version=2024-07-01
107+
POST https://[service name].search.windows.net/datasources?api-version=@search.rerankerBoostedScore
108108
Content-Type: application/json
109109
api-key: [Search service admin key]
110110
{
@@ -234,7 +234,7 @@ In a [search index](search-what-is-an-index.md), add fields to accept the source
234234
1. [Create or update an index](/rest/api/searchservice/indexes/create) to define search fields that store data:
235235

236236
```http
237-
POST https://[service name].search.windows.net/indexes?api-version=2024-07-01
237+
POST https://[service name].search.windows.net/indexes?api-version=@search.rerankerBoostedScore
238238
Content-Type: application/json
239239
api-key: [Search service admin key]
240240
{
@@ -282,7 +282,7 @@ Once the index and data source have been created, you're ready to create the ind
282282
1. [Create or update an indexer](/rest/api/searchservice/indexers/create) by giving it a name and referencing the data source and target index:
283283
284284
```http
285-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
285+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
286286
Content-Type: application/json
287287
api-key: [search service admin key]
288288
{
@@ -323,7 +323,7 @@ To monitor the indexer status and execution history, check the indexer execution
323323
324324
### [**REST**](#tab/rest-check-indexer)
325325
```http
326-
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
326+
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=@search.rerankerBoostedScore
327327
Content-Type: application/json
328328
api-key: [admin key]
329329
```
@@ -427,7 +427,7 @@ The `softDeleteColumnName` must be a top-level field in the index. Using nested
427427
The following example creates a data source with a soft-deletion policy:
428428

429429
```http
430-
POST https://[service name].search.windows.net/datasources?api-version=2024-07-01
430+
POST https://[service name].search.windows.net/datasources?api-version=@search.rerankerBoostedScore
431431
Content-Type: application/json
432432
api-key: [Search service admin key]
433433

‎articles/search/search-howto-index-json-blobs.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ The blob indexer parses the JSON document into a single search document, loading
6161
Although the default behavior is one search document per JSON blob, setting the **`json`** parsing mode changes the internal field mappings for content, promoting fields inside `content` to actual fields in the search index. An example indexer definition for the **`json`** parsing mode might look like this:
6262

6363
```http
64-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
64+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
6565
Content-Type: application/json
6666
api-key: [admin key]
6767
@@ -100,7 +100,7 @@ Alternatively, you can use the JSON array option. This option is useful when blo
100100
The `parameters` property on the indexer contains parsing mode values. For a JSON array, the indexer definition should look similar to the following example.
101101

102102
```http
103-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
103+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
104104
Content-Type: application/json
105105
api-key: [admin key]
106106
@@ -159,7 +159,7 @@ If your blob contains multiple JSON entities separated by a newline, and you wan
159159
For JSON lines, the indexer definition should look similar to the following example.
160160

161161
```http
162-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
162+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
163163
Content-Type: application/json
164164
api-key: [admin key]
165165

‎articles/search/search-howto-index-plaintext-blobs.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ An alternative third option for breaking content into multiple parts requires ad
3838
To index plain text blobs, create or update an indexer definition with the `parsingMode` configuration property set to `text` on a [Create Indexer](/rest/api/searchservice/indexers/create) request:
3939

4040
```http
41-
PUT https://[service name].search.windows.net/indexers/[indexer name]?api-version=2024-07-01
41+
PUT https://[service name].search.windows.net/indexers/[indexer name]?api-version=@search.rerankerBoostedScore
4242
Content-Type: application/json
4343
api-key: [admin key]
4444
@@ -62,7 +62,7 @@ By default, the `UTF-8` encoding is assumed. To specify a different encoding, us
6262
Parsing modes are specified in the indexer definition.
6363

6464
```http
65-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
65+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
6666
Content-Type: application/json
6767
api-key: [admin key]
6868

‎articles/search/search-howto-indexing-azure-blob-storage.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -178,7 +178,7 @@ In a [search index](search-what-is-an-index.md), add fields to accept the conten
178178
1. [Create or update an index](/rest/api/searchservice/indexes/create-or-update) to define search fields that will store blob content and metadata:
179179

180180
```http
181-
POST https://[service name].search.windows.net/indexes?api-version=2024-07-01
181+
POST https://[service name].search.windows.net/indexes?api-version=@search.rerankerBoostedScore
182182
{
183183
"name" : "my-search-index",
184184
"fields": [
@@ -214,7 +214,7 @@ Once the index and data source have been created, you're ready to create the ind
214214
1. [Create or update an indexer](/rest/api/searchservice/indexers/create-or-update) by giving it a name and referencing the data source and target index:
215215

216216
```http
217-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
217+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
218218
{
219219
"name" : "my-blob-indexer",
220220
"dataSourceName" : "my-blob-datasource",
@@ -271,7 +271,7 @@ To illustrate, let's consider an example of two indexers, pulling data from two
271271
First indexer definition example:
272272

273273
```http
274-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
274+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
275275
{
276276
"name" : "my-blob-indexer1",
277277
"dataSourceName" : "my-blob-datasource1",
@@ -294,7 +294,7 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
294294
Second indexer definition that runs in parallel example:
295295

296296
```http
297-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
297+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
298298
{
299299
"name" : "my-blob-indexer2",
300300
"dataSourceName" : "my-blob-datasource2",
@@ -320,7 +320,7 @@ POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
320320
To monitor the indexer status and execution history, send a [Get Indexer Status](/rest/api/searchservice/indexers/get-status) request:
321321

322322
```http
323-
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
323+
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=@search.rerankerBoostedScore
324324
Content-Type: application/json
325325
api-key: [admin key]
326326
```
@@ -372,7 +372,7 @@ By default, the blob indexer stops as soon as it encounters a blob with an unsup
372372
There are five indexer properties that control the indexer's response when errors occur.
373373

374374
```http
375-
PUT /indexers/[indexer name]?api-version=2024-07-01
375+
PUT /indexers/[indexer name]?api-version=@search.rerankerBoostedScore
376376
{
377377
"parameters" : {
378378
"maxFailedItems" : 10,

‎articles/search/search-howto-indexing-azure-tables.md‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ The data source definition specifies the source data to index, credentials, and
8989
1. [Create or update a data source](/rest/api/searchservice/data-sources/create-or-update) to set its definition:
9090

9191
```http
92-
POST https://[service name].search.windows.net/datasources?api-version=2024-07-01
92+
POST https://[service name].search.windows.net/datasources?api-version=@search.rerankerBoostedScore
9393
{
9494
"name": "my-table-storage-ds",
9595
"description": null,
@@ -175,7 +175,7 @@ In a [search index](search-what-is-an-index.md), add fields to accept the conten
175175
1. [Create or update an index](/rest/api/searchservice/indexes/create) to define search fields that will store content from entities:
176176

177177
```http
178-
POST https://[service name].search.windows.net/indexes?api-version=2024-07-01
178+
POST https://[service name].search.windows.net/indexes?api-version=@search.rerankerBoostedScore
179179
{
180180
"name" : "my-search-index",
181181
"fields": [
@@ -215,7 +215,7 @@ Once you have an index and data source, you're ready to create the indexer. Inde
215215
1. [Create or update an indexer](/rest/api/searchservice/indexers/create) by giving it a name and referencing the data source and target index:
216216

217217
```http
218-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
218+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
219219
{
220220
"name" : "my-table-indexer",
221221
"dataSourceName" : "my-table-storage-ds",
@@ -264,7 +264,7 @@ To monitor the indexer status and execution history, check the indexer execution
264264
### [**REST**](#tab/rest-check-indexer)
265265

266266
```http
267-
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=2024-07-01
267+
GET https://myservice.search.windows.net/indexers/myindexer/status?api-version=@search.rerankerBoostedScore
268268
Content-Type: application/json
269269
api-key: [admin key]
270270
```

‎articles/search/search-howto-managed-identities-cosmos-db.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ When you're connecting with a system-assigned managed identity, the only change
105105
Here's an example using the [Create Data Source](/rest/api/searchservice/data-sources/create) REST API that exercises the _modern_ approach.
106106

107107
```http
108-
POST https://[service name].search.windows.net/datasources?api-version=2024-07-01
108+
POST https://[service name].search.windows.net/datasources?api-version=@search.rerankerBoostedScore
109109
{
110110
"name": "my-cosmosdb-ds",
111111
"type": "cosmosdb",

‎articles/search/search-howto-managed-identities-sql.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ When you're connecting with a system-assigned managed identity, the only change
100100
Here's an example of how to create a data source to index data from a storage account using the [Create Data Source](/rest/api/searchservice/data-sources/create) REST API and a managed identity connection string. The managed identity connection string format is the same for the REST API, .NET SDK, and the Azure portal.
101101

102102
```http
103-
POST https://[service name].search.windows.net/datasources?api-version=2024-07-01
103+
POST https://[service name].search.windows.net/datasources?api-version=@search.rerankerBoostedScore
104104
Content-Type: application/json
105105
api-key: [admin key]
106106
@@ -154,7 +154,7 @@ The index specifies the fields in a document, attributes, and other constructs t
154154
Here's a [Create Index](/rest/api/searchservice/indexes/create) REST API call with a searchable `booktitle` field:
155155
156156
```http
157-
POST https://[service name].search.windows.net/indexes?api-version=2024-07-01
157+
POST https://[service name].search.windows.net/indexes?api-version=@search.rerankerBoostedScore
158158
Content-Type: application/json
159159
api-key: [admin key]
160160
@@ -174,7 +174,7 @@ An indexer connects a data source with a target search index, and provides a sch
174174
Here's a [Create Indexer](/rest/api/searchservice/indexers/create) REST API call with an Azure SQL indexer definition. The indexer runs when you submit the request.
175175
176176
```http
177-
POST https://[service name].search.windows.net/indexers?api-version=2024-07-01
177+
POST https://[service name].search.windows.net/indexers?api-version=@search.rerankerBoostedScore
178178
Content-Type: application/json
179179
api-key: [admin key]
180180

0 commit comments

Comments
 (0)