mixpeek 0.81.8 → 0.81.10

package/dist/api/analytics-api.d.ts

@@ -220,7 +220,7 @@ export declare const AnalyticsApiAxiosParamCreator: (configuration?: Configurati
      */
     getExtractorBreakdownAnalyticsPerformanceEngine: (hours?: number, startDate?: string, endDate?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {string} [extractorName] Filter by extractor
      * @param {number} [hours] Hours of history
@@ -611,7 +611,7 @@ export declare const AnalyticsApiFp: (configuration?: Configuration) => {
      */
     getExtractorBreakdownAnalyticsPerformanceEngine(hours?: number, startDate?: string, endDate?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ExtractorBreakdownResponse>>;
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {string} [extractorName] Filter by extractor
      * @param {number} [hours] Hours of history
@@ -980,7 +980,7 @@ export declare const AnalyticsApiFactory: (configuration?: Configuration, basePa
      */
     getExtractorBreakdownAnalyticsPerformanceEngine(requestParameters?: AnalyticsApiGetExtractorBreakdownAnalyticsPerformanceEngineRequest, options?: RawAxiosRequestConfig): AxiosPromise<ExtractorBreakdownResponse>;
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {AnalyticsApiGetExtractorPerformanceAnalyticsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
@@ -2243,7 +2243,7 @@ export declare class AnalyticsApi extends BaseAPI {
      */
     getExtractorBreakdownAnalyticsPerformanceEngine(requestParameters?: AnalyticsApiGetExtractorBreakdownAnalyticsPerformanceEngineRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<ExtractorBreakdownResponse, any, {}>>;
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {AnalyticsApiGetExtractorPerformanceAnalyticsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.

package/dist/api/analytics-extractors-api.d.ts

@@ -18,7 +18,7 @@ import { type RequestArgs, BaseAPI } from '../base';
  */
 export declare const AnalyticsExtractorsApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {string} [extractorName] Filter by extractor
      * @param {number} [hours] Hours of history
@@ -33,7 +33,7 @@ export declare const AnalyticsExtractorsApiAxiosParamCreator: (configuration?: C
  */
 export declare const AnalyticsExtractorsApiFp: (configuration?: Configuration) => {
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {string} [extractorName] Filter by extractor
      * @param {number} [hours] Hours of history
@@ -50,7 +50,7 @@ export declare const AnalyticsExtractorsApiFp: (configuration?: Configuration) =
  */
 export declare const AnalyticsExtractorsApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {AnalyticsExtractorsApiGetExtractorPerformanceAnalyticsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
@@ -87,7 +87,7 @@ export interface AnalyticsExtractorsApiGetExtractorPerformanceAnalyticsRequest {
  */
 export declare class AnalyticsExtractorsApi extends BaseAPI {
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {AnalyticsExtractorsApiGetExtractorPerformanceAnalyticsRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.

package/dist/api/collection-documents-api.d.ts

@@ -43,7 +43,7 @@ export declare const CollectionDocumentsApiAxiosParamCreator: (configuration?: C
      */
     aggregateDocuments: (collectionIdentifier: string, documentAggregationRequest: DocumentAggregationRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
      * @summary Batch Delete Documents
      * @param {string} collectionIdentifier The ID of the collection to delete documents from.
      * @param {BatchDeleteDocumentsRequest} batchDeleteDocumentsRequest
@@ -52,7 +52,7 @@ export declare const CollectionDocumentsApiAxiosParamCreator: (configuration?: C
      */
     batchDelete: (collectionIdentifier: string, batchDeleteDocumentsRequest: BatchDeleteDocumentsRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
      * @summary Batch Update Documents
      * @param {string} collectionIdentifier The ID of the collection to update documents in.
      * @param {BatchUpdateDocumentsRequest} batchUpdateDocumentsRequest
@@ -218,7 +218,7 @@ export declare const CollectionDocumentsApiFp: (configuration?: Configuration) =
      */
     aggregateDocuments(collectionIdentifier: string, documentAggregationRequest: DocumentAggregationRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<DocumentAggregationResponse>>;
     /**
-     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
      * @summary Batch Delete Documents
      * @param {string} collectionIdentifier The ID of the collection to delete documents from.
      * @param {BatchDeleteDocumentsRequest} batchDeleteDocumentsRequest
@@ -227,7 +227,7 @@ export declare const CollectionDocumentsApiFp: (configuration?: Configuration) =
      */
     batchDelete(collectionIdentifier: string, batchDeleteDocumentsRequest: BatchDeleteDocumentsRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<BatchDeleteDocumentsResponse>>;
     /**
-     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
      * @summary Batch Update Documents
      * @param {string} collectionIdentifier The ID of the collection to update documents in.
      * @param {BatchUpdateDocumentsRequest} batchUpdateDocumentsRequest
@@ -392,7 +392,7 @@ export declare const CollectionDocumentsApiFactory: (configuration?: Configurati
      */
     aggregateDocuments(requestParameters: CollectionDocumentsApiAggregateDocumentsRequest, options?: RawAxiosRequestConfig): AxiosPromise<DocumentAggregationResponse>;
     /**
-     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
      * @summary Batch Delete Documents
      * @param {CollectionDocumentsApiBatchDeleteRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
@@ -400,7 +400,7 @@ export declare const CollectionDocumentsApiFactory: (configuration?: Configurati
      */
     batchDelete(requestParameters: CollectionDocumentsApiBatchDeleteRequest, options?: RawAxiosRequestConfig): AxiosPromise<BatchDeleteDocumentsResponse>;
     /**
-     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
      * @summary Batch Update Documents
      * @param {CollectionDocumentsApiBatchUpdateRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
@@ -953,7 +953,7 @@ export declare class CollectionDocumentsApi extends BaseAPI {
      */
     aggregateDocuments(requestParameters: CollectionDocumentsApiAggregateDocumentsRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<DocumentAggregationResponse, any, {}>>;
     /**
-     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
      * @summary Batch Delete Documents
      * @param {CollectionDocumentsApiBatchDeleteRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.
@@ -962,7 +962,7 @@ export declare class CollectionDocumentsApi extends BaseAPI {
      */
     batchDelete(requestParameters: CollectionDocumentsApiBatchDeleteRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<BatchDeleteDocumentsResponse, any, {}>>;
     /**
-     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
      * @summary Batch Update Documents
      * @param {CollectionDocumentsApiBatchUpdateRequest} requestParameters Request parameters.
      * @param {*} [options] Override http request option.

package/dist/index.js

@@ -2442,7 +2442,7 @@ var AnalyticsApiAxiosParamCreator = function(configuration) {
       };
     },
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {string} [extractorName] Filter by extractor
      * @param {number} [hours] Hours of history
@@ -3458,7 +3458,7 @@ var AnalyticsApiFp = function(configuration) {
       return (axios2, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios5__default.default, BASE_PATH, configuration)(axios2, localVarOperationServerBasePath || basePath);
     },
     /**
-     * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+     * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
      * @summary Get Extractor Performance
      * @param {string} [extractorName] Filter by extractor
      * @param {number} [hours] Hours of history
@@ -3982,7 +3982,7 @@ var AnalyticsApi = class extends BaseAPI {
     return AnalyticsApiFp(this.configuration).getExtractorBreakdownAnalyticsPerformanceEngine(requestParameters.hours, requestParameters.startDate, requestParameters.endDate, options).then((request) => request(this.axios, this.basePath));
   }
   /**
-   * Get feature extraction performance metrics.  Returns performance metrics for feature extractors including: - Total executions per extractor - Average duration - P95/P99 latencies - Success/failure rates  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
+   * Get feature extraction performance metrics.  Returns per-extractor execution metrics from the ``extraction_events`` ClickHouse table over the last ``hours`` (namespace-scoped), one row per (extractor_name, version): - Total executions per extractor - Average duration + P95/P99 latencies - Success/failure counts and success rate  Returns an empty array when no extraction has run in the window or analytics is unavailable.  **Example:** ```bash GET /v1/analytics/extractors/performance?hours=24 GET /v1/analytics/extractors/performance?extractor_name=text_extractor&hours=168 ```
    * @summary Get Extractor Performance
    * @param {AnalyticsApiGetExtractorPerformanceAnalyticsRequest} requestParameters Request parameters.
    * @param {*} [options] Override http request option.
@@ -10414,7 +10414,7 @@ var CollectionDocumentsApiAxiosParamCreator = function(configuration) {
       };
     },
     /**
-     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
      * @summary Batch Delete Documents
      * @param {string} collectionIdentifier The ID of the collection to delete documents from.
      * @param {BatchDeleteDocumentsRequest} batchDeleteDocumentsRequest 
@@ -10444,7 +10444,7 @@ var CollectionDocumentsApiAxiosParamCreator = function(configuration) {
       };
     },
     /**
-     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
      * @summary Batch Update Documents
      * @param {string} collectionIdentifier The ID of the collection to update documents in.
      * @param {BatchUpdateDocumentsRequest} batchUpdateDocumentsRequest 
@@ -10943,7 +10943,7 @@ var CollectionDocumentsApiFp = function(configuration) {
       return (axios2, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios5__default.default, BASE_PATH, configuration)(axios2, localVarOperationServerBasePath || basePath);
     },
     /**
-     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+     * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
      * @summary Batch Delete Documents
      * @param {string} collectionIdentifier The ID of the collection to delete documents from.
      * @param {BatchDeleteDocumentsRequest} batchDeleteDocumentsRequest 
@@ -10957,7 +10957,7 @@ var CollectionDocumentsApiFp = function(configuration) {
       return (axios2, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios5__default.default, BASE_PATH, configuration)(axios2, localVarOperationServerBasePath || basePath);
     },
     /**
-     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+     * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
      * @summary Batch Update Documents
      * @param {string} collectionIdentifier The ID of the collection to update documents in.
      * @param {BatchUpdateDocumentsRequest} batchUpdateDocumentsRequest 
@@ -11186,7 +11186,7 @@ var CollectionDocumentsApi = class extends BaseAPI {
     return CollectionDocumentsApiFp(this.configuration).aggregateDocuments(requestParameters.collectionIdentifier, requestParameters.documentAggregationRequest, options).then((request) => request(this.axios, this.basePath));
   }
   /**
-   * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"archived\"}]}     }     ```
+   * Batch delete multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'document_ids\' array    - Deletes specific documents by ID    - Returns detailed per-document results    - Maximum 1000 documents per batch  2. Filter mode: Provide \'filters\' to delete all matching documents    - Deletes ALL documents matching the filters    - Returns total count only    - Use with caution - can delete many documents  Key Features: - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection - Automatic document count update for the collection - Efficient bulk deletion  Examples:     Explicit IDs mode:     ```json     {         \"document_ids\": [\"doc_123\", \"doc_456\", \"doc_789\"]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"archived\"}]}     }     ```
    * @summary Batch Delete Documents
    * @param {CollectionDocumentsApiBatchDeleteRequest} requestParameters Request parameters.
    * @param {*} [options] Override http request option.
@@ -11197,7 +11197,7 @@ var CollectionDocumentsApi = class extends BaseAPI {
     return CollectionDocumentsApiFp(this.configuration).batchDelete(requestParameters.collectionIdentifier, requestParameters.batchDeleteDocumentsRequest, options).then((request) => request(this.axios, this.basePath));
   }
   /**
-   * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode:     ```json     {         \"filters\": {\"must\": [{\"key\": \"metadata.status\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
+   * Batch update multiple documents by explicit IDs or filters.  Supports TWO modes: 1. Explicit IDs mode: Provide \'updates\' array with document_id + update_data for each document    - Each document can have DIFFERENT update_data    - Returns detailed per-document results  2. Filter mode: Provide \'filters\' + \'update_data\' to update all matching documents    - All documents receive the SAME update_data    - Returns total count only  Key Features: - Update any document field except vectors (metadata, internal_metadata, source_blobs, etc.) - Maximum 1000 documents per batch in explicit mode - Per-document success/failure reporting in explicit mode - Validates documents exist in the specified collection  Examples:     Explicit IDs mode:     ```json     {         \"updates\": [             {\"document_id\": \"doc_123\", \"update_data\": {\"metadata\": {\"status\": \"processed\"}}},             {\"document_id\": \"doc_456\", \"update_data\": {\"metadata\": {\"status\": \"archived\"}}}         ]     }     ```      Filter mode (logical AND/OR/NOT shape — NOT MVS-native must/key):     ```json     {         \"filters\": {\"AND\": [{\"field\": \"metadata.status\", \"operator\": \"eq\", \"value\": \"pending\"}]},         \"update_data\": {\"metadata\": {\"status\": \"processed\"}}     }     ```
    * @summary Batch Update Documents
    * @param {CollectionDocumentsApiBatchUpdateRequest} requestParameters Request parameters.
    * @param {*} [options] Override http request option.