Merge pull request #7332 from HeidiSteen/heidist-0901

bulk API version change

Author: prmerger-automator[bot]

articles/search/cognitive-search-attach-cognitive-services.md

@@ -235,7 +235,7 @@ Enrichments are billable operations. If you no longer need to call Azure AI serv
 1. Remove the key in the body of the definition, and then send the request:
 
     ```http
-    PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=2024-07-01
+    PUT https://[servicename].search.windows.net/skillsets/[skillset name]?api-version=@search.rerankerBoostedScore
     api-key: [admin key]
     Content-Type: application/json
     {

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

@@ -105,7 +105,7 @@ The following example shows a hybrid query request using the REST API.
 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. 
 
 ```http
-POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
+POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
 Content-Type: application/json
 api-key: {{admin-api-key}}
 {
@@ -240,7 +240,7 @@ This section has multiple query examples that illustrate hybrid query patterns.
 This example adds a filter, which is applied to the `filterable` nonvector fields of the search index.
 
 ```http
-POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
+POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
 Content-Type: application/json
 api-key: {{admin-api-key}}
 {
@@ -324,7 +324,7 @@ Assuming that you [have semantic ranker](semantic-how-to-enable-disable.md) and
 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.
 
 ```http
-POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
+POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
 Content-Type: application/json
 api-key: {{admin-api-key}}
 {
@@ -365,7 +365,7 @@ api-key: {{admin-api-key}}
 Here's the last query in the collection. It's the same semantic hybrid query as the previous example, but with a filter.
 
 ```http
-POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=2024-07-01
+POST https://{{search-service-name}}.search.windows.net/indexes/{{index-name}}/docs/search?api-version=@search.rerankerBoostedScore
 Content-Type: application/json
 api-key: {{admin-api-key}}
 {

articles/search/hybrid-search-overview.md

@@ -34,7 +34,7 @@ Hybrid search is predicated on having a search index that contains fields of var
 A representative hybrid query might be as follows (notice that the vector queries have placeholder values for brevity):
 
 ```http
-POST https://{{searchServiceName}}.search.windows.net/indexes/hotels-vector-quickstart/docs/search?api-version=2024-07-01
+POST https://{{searchServiceName}}.search.windows.net/indexes/hotels-vector-quickstart/docs/search?api-version=@search.rerankerBoostedScore
   content-type: application/JSON
 {
     "count": true,

articles/search/index-add-scoring-profiles.md

@@ -77,7 +77,7 @@ The following definition shows a simple profile named "geo". This example boosts
 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.
 
 ```http
-POST /indexes/hotels/docs&api-version=2024-07-01
+POST /indexes/hotels/docs&api-version=@search.rerankerBoostedScore
 {
     "search": "inn",
     "scoringProfile": "geo",

articles/search/index-add-suggesters.md

@@ -161,7 +161,7 @@ In a search application, client code should use a library like [jQuery UI Autoco
 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.
 
 ```http
-POST /indexes/myxboxgames/docs/autocomplete?search&api-version=2024-07-01
+POST /indexes/myxboxgames/docs/autocomplete?search&api-version=@search.rerankerBoostedScore
 {
   "search": "minecraf",
   "suggesterName": "sg"

articles/search/index-ranking-similarity.md

@@ -43,7 +43,7 @@ BM25 ranking provides two parameters for tuning the relevance score calculation.
 1. Use a [Create or Update Index](/rest/api/searchservice/indexes/create) request to set BM25 parameters:
 
     ```http
-    PUT [service-name].search.windows.net/indexes/[index-name]?api-version=2024-07-01&allowIndexDowntime=true
+    PUT [service-name].search.windows.net/indexes/[index-name]?api-version=@search.rerankerBoostedScore&allowIndexDowntime=true
     {
         "similarity": {
             "@odata.type": "#Microsoft.Azure.Search.BM25Similarity",
@@ -84,7 +84,7 @@ The following links describe the Similarity property in the Azure SDKs.
 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:
 
 ```http
-PUT [service-name].search.windows.net/indexes/[index name]?api-version=2024-07-01
+PUT [service-name].search.windows.net/indexes/[index name]?api-version=@search.rerankerBoostedScore
 {
     "name": "indexName",
     "fields": [

articles/search/index-similarity-and-scoring.md

@@ -97,7 +97,7 @@ By default, the score of a document is calculated based on statistical propertie
 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)).
 
 ```http
-POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=2024-07-01
+POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=@search.rerankerBoostedScore
 {
     "search": "<query string>",
     "scoringStatistics": "global"
@@ -107,7 +107,7 @@ POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-ve
 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.
 
 ```http
-POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=2024-07-01
+POST https://[service name].search.windows.net/indexes/hotels/docs/search?api-version=@search.rerankerBoostedScore
 {
     "search": "<query string>",
     "sessionId": "<string>"

articles/search/knowledge-store-create-rest.md

@@ -92,7 +92,7 @@ A valid API key establishes trust, on a per request basis, between the applicati
 
     ```http
     ### Create a new index
-    POST {{baseUrl}}/indexes?api-version=2024-07-01  HTTP/1.1
+    POST {{baseUrl}}/indexes?api-version=@search.rerankerBoostedScore  HTTP/1.1
         Content-Type: application/json
         api-key: {{apiKey}}
     
@@ -124,7 +124,7 @@ A valid API key establishes trust, on a per request basis, between the applicati
 
     ```http
     ### Create a data source
-    POST {{baseUrl}}/datasources?api-version=2024-07-01  HTTP/1.1
+    POST {{baseUrl}}/datasources?api-version=@search.rerankerBoostedScore  HTTP/1.1
       Content-Type: application/json
       api-key: {{apiKey}}
     
@@ -155,7 +155,7 @@ A skillset defines enrichments (skills) and your knowledge store. [Create Skills
 
     ```http
     ### Create a skillset
-    POST {{baseUrl}}/skillsets?api-version=2024-07-01  HTTP/1.1
+    POST {{baseUrl}}/skillsets?api-version=@search.rerankerBoostedScore  HTTP/1.1
         Content-Type: application/json
         api-key: {{apiKey}}
     
@@ -322,7 +322,7 @@ A skillset defines enrichments (skills) and your knowledge store. [Create Skills
 
     ```http
     ### Create indexer
-    POST {{baseUrl}}/indexers?api-version=2024-07-01  HTTP/1.1
+    POST {{baseUrl}}/indexers?api-version=@search.rerankerBoostedScore  HTTP/1.1
         Content-Type: application/json
         api-key: {{apiKey}}
     
@@ -370,7 +370,7 @@ After you send each request, the search service should respond with a 201 succes
 
 ```http
 ### Get Indexer Status (wait several minutes for the indexer to complete)
-GET {{baseUrl}}/indexers/hotel-reviews-kstore-idxr/status?api-version=2024-07-01  HTTP/1.1
+GET {{baseUrl}}/indexers/hotel-reviews-kstore-idxr/status?api-version=@search.rerankerBoostedScore  HTTP/1.1
   Content-Type: application/json
   api-key: {{apiKey}}
 ```
@@ -379,7 +379,7 @@ After several minutes, you can query the index to inspect the content. Even if y
 
 ```http
 ### Query the index (indexer status must be "success" before querying the index)
-POST {{baseUrl}}/indexes/hotel-reviews-kstore-idxr/docs/search?api-version=2024-07-01  HTTP/1.1
+POST {{baseUrl}}/indexes/hotel-reviews-kstore-idxr/docs/search?api-version=@search.rerankerBoostedScore  HTTP/1.1
   Content-Type: application/json
   api-key: {{apiKey}}
   

articles/search/monitor-azure-cognitive-search-data-reference.md

@@ -160,7 +160,7 @@ The following example illustrates a resource log that includes common properties
 | Resource | String | Resource ID. For example: `/subscriptions/<your-subscription-id>/resourceGroups/<your-resource-group-name>/providers/Microsoft.Search/searchServices/<your-search-service-name>` |
 | Category | String | "OperationLogs". This value is a constant. OperationLogs is the only category used for resource logs. |
 | OperationName | String |  The name of the operation (see the [full list of operations](#resource-log-search-ops)). An example is `Query.Search` |
-| OperationVersion | String | The api-version used on the request. For example: `2024-07-01` |
+| OperationVersion | String | The api-version used on the request. For example: `@search.rerankerBoostedScore` |
 | ResultType | String |"Success". Other possible values: Success or Failure |
 | ResultSignature | Int | An HTTP result code. For example: `200` |
 | DurationMS | Int | Duration of the operation in milliseconds. |
@@ -177,7 +177,7 @@ The following properties are specific to Azure AI Search.
 | Description_s | String | The operation's endpoint. For example: `GET /indexes('content')/docs` |
 | Documents_d | Int | Number of documents processed. |
 | IndexName_s | String | Name of the index associated with the operation. |
-| Query_s | String | The query parameters used in the request. For example: `?search=beach access&$count=true&api-version=2024-07-01` |
+| Query_s | String | The query parameters used in the request. For example: `?search=beach access&$count=true&api-version=@search.rerankerBoostedScore` |
 
 <a name="resource-log-search-ops"></a>
 

articles/search/query-lucene-syntax.md

@@ -24,7 +24,7 @@ To use full Lucene syntax, set the queryType to `full` and pass in a query expre
 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).  
 
 ```http
-POST /indexes/hotels-sample-index/docs/search?api-version=2024-07-01
+POST /indexes/hotels-sample-index/docs/search?api-version=@search.rerankerBoostedScore
 {
   "queryType": "full",
   "search": "category:budget AND \"recently renovated\"^3",