fix(java): send request bodies with Content-Length instead of chunked encoding (generated)

algolia/api-clients-automation#7069

Co-authored-by: algolia-api-clients-automation-bot[bot] <288895823+algolia-api-clients-automation-bot[bot]@users.noreply.github.com>
Co-authored-by: Thomas Raffray <Fluf22@users.noreply.github.com>

Author: algolia-api-clients-automation-bot[bot]

packages/agent-studio/src/agentStudioClient.ts

@@ -501,7 +501,7 @@ export function createAgentStudioClient({
     },
 
     /**
-     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request - Request 2: User approves -> Execute tool -> Agent continues with result.
+     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request. - Request 2: User approves -> Execute tool -> Agent continues with result.
      *
      * Required API Key ACLs:
      *  - search
@@ -577,7 +577,7 @@ export function createAgentStudioClient({
       return transporter.request(request, requestOptions);
     },
     /**
-     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request - Request 2: User approves -> Execute tool -> Agent continues with result.
+     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request. - Request 2: User approves -> Execute tool -> Agent continues with result.
      *
      * Resolves with the full HTTP response information: status code, headers (when the requester captures them), raw body and deserialized data. Bypasses the requests and responses caches: always performs the API call.
      *
@@ -656,7 +656,7 @@ export function createAgentStudioClient({
       return transporter.requestWithHttpInfo(request, requestOptions);
     },
     /**
-     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request - Request 2: User approves -> Execute tool -> Agent continues with result. (raw streaming version).
+     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request. - Request 2: User approves -> Execute tool -> Agent continues with result. (raw streaming version).
      *
      * Yields raw {@link ServerSentEvent} objects. Each event's `data` field contains a JSON-encoded `{ [key: string]: any; }` string.
      *
@@ -724,7 +724,7 @@ export function createAgentStudioClient({
       return transporter.requestStream(request, requestOptions);
     },
     /**
-     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request - Request 2: User approves -> Execute tool -> Agent continues with result. (streaming version).
+     * Create a completion for the specified agent.  This endpoint handles two types of requests: 1. Normal completion request: User message -> Agent response 2. Tool approval response: User approval -> Execute tool -> Agent response  Tool Approval Flow (for MCP tools with requiresApproval: true): - Request 1: User sends message -> Agent requests tool call -> Return approval request. - Request 2: User approves -> Execute tool -> Agent continues with result. (streaming version).
      *
      * Yields {@link StreamEvent} objects wrapping parsed `{ [key: string]: any; }` payloads.
      *

packages/algoliasearch/builds/models.ts

@@ -25,6 +25,7 @@ import type {
   AroundPrecision,
   AroundRadius,
   AroundRadiusAll,
+  AttributeCriteriaComputedBy,
   AutomaticFacetFilter,
   AutomaticFacetFilters,
   Banner,
@@ -203,6 +204,7 @@ export type {
   AroundPrecision,
   AroundRadius,
   AroundRadiusAll,
+  AttributeCriteriaComputedBy,
   AutomaticFacetFilter,
   AutomaticFacetFilters,
   Banner,

packages/algoliasearch/lite/model/apiKey.ts

@@ -17,7 +17,7 @@ export type ApiKey = {
   description?: string | undefined;
 
   /**
-   * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application.  You can use leading and trailing wildcard characters (`*`):  - `dev_*` matches all indices starting with \"dev_\" - `*_dev` matches all indices ending with \"_dev\" - `*_products_*` matches all indices containing \"_products_\".
+   * Index names or patterns that this API key can access. By default, an API key can access all indices in the same application.  You can use leading and trailing wildcard characters (`*`):  - `dev_*` matches all indices starting with \"dev_\". - `*_dev` matches all indices ending with \"_dev\". - `*_products_*` matches all indices containing \"_products_\".
    */
   indexes?: Array<string> | undefined;
 
@@ -37,7 +37,7 @@ export type ApiKey = {
   queryParameters?: string | undefined;
 
   /**
-   * Allowed HTTP referrers for this API key.  By default, all referrers are allowed. You can use leading and trailing wildcard characters (`*`):  - `https://algolia.com/_*` allows all referrers starting with \"https://algolia.com/\" - `*.algolia.com` allows all referrers ending with \".algolia.com\" - `*algolia.com*` allows all referrers in the domain \"algolia.com\".  Like all HTTP headers, referrers can be spoofed. Don\'t rely on them to secure your data. For more information, see [HTTP referrer restrictions](https://www.algolia.com/doc/guides/security/security-best-practices/#http-referrers-restrictions).
+   * Allowed HTTP referrers for this API key.  By default, all referrers are allowed. You can use leading and trailing wildcard characters (`*`):  - `https://algolia.com/_*` allows all referrers starting with \"https://algolia.com/\". - `*.algolia.com` allows all referrers ending with \".algolia.com\". - `*algolia.com*` allows all referrers in the domain \"algolia.com\".  Like all HTTP headers, referrers can be spoofed. Don\'t rely on them to secure your data. For more information, see [HTTP referrer restrictions](https://www.algolia.com/doc/guides/security/security-best-practices/#http-referrers-restrictions).
    */
   referers?: Array<string> | undefined;
 

packages/algoliasearch/lite/model/attributeCriteriaComputedBy.ts

@@ -0,0 +1,6 @@
+// Code generated by OpenAPI Generator (https://openapi-generator.tech), manual changes will be lost - read more on https://github.com/algolia/api-clients-automation. DO NOT EDIT.
+
+/**
+ * Strategy for computing the Attribute ranking criterion. This mainly affects multi-word queries with matches in more than one attribute.  The `ranking` setting decides whether `best` takes effect. When Attribute comes after Proximity, which is the default order, the engine always uses the `minProximity` strategy and ignores `best`. To select `best`, move Attribute before Proximity in `ranking`. The `sum` strategy applies in both orders.  - `minProximity`.   Pick the best matching attribute from the attributes that form the best proximity score.   On an ordered attribute, the match position breaks ties. - `best`.   Pick the best matching attribute from all attributes that match any query word.   On an ordered attribute, the match position breaks ties. - `sum`.   Add up a score for every query word instead of picking one attribute.   Each word\'s score comes from the attribute it matched, and from its position in that attribute when the attribute is ordered.   A query word that matches nothing adds a large penalty.   A record with a lower total ranks higher.   A record therefore cannot rank high only because one word of a multi-word query matched a top attribute.   Use `sum` with short, relevant attributes, and set long-text attributes to unordered.
+ */
+export type AttributeCriteriaComputedBy = 'minProximity' | 'best' | 'sum';