@alien_intelligence/data-api-client 2.3.2 → 2.6.0

package/dist/src/apis/AdminApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/AdminApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DatasetsApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DatasetsApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DefaultApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/DefaultApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/EmbeddingsApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/EmbeddingsApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/EntriesApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -193,7 +193,7 @@ export interface EntriesApiInterface {
      */
     getEntryApiV1EntriesEntryIdGet(requestParameters: GetEntryApiV1EntriesEntryIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Entry>;
     /**
-     * Get processed content for a single entry
+     * The entry\'s processed content. `text` is always a string when present: the canonical text every offset this API returns indexes into (segment `char_start`/`char_end`, keyword-search snippet `context.offset`). Content stored with `text` as a list of chunks is served with the chunks joined by one space.
      * @summary Get Entry Content
      * @param {number} entryId
      * @param {*} [options] Override http request option.
@@ -204,7 +204,7 @@ export interface EntriesApiInterface {
         [key: string]: any;
     }>>;
     /**
-     * Get processed content for a single entry
+     * The entry\'s processed content. `text` is always a string when present: the canonical text every offset this API returns indexes into (segment `char_start`/`char_end`, keyword-search snippet `context.offset`). Content stored with `text` as a list of chunks is served with the chunks joined by one space.
      * Get Entry Content
      */
     getEntryContentApiV1EntriesEntryIdContentGet(requestParameters: GetEntryContentApiV1EntriesEntryIdContentGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{
@@ -297,7 +297,7 @@ export interface EntriesApiInterface {
      */
     moveEntryApiV1EntriesEntryIdMovePost(requestParameters: MoveEntryApiV1EntriesEntryIdMovePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<MoveEntryResponse>;
     /**
-     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  A reset that deleted anything (a manifest section, an object under `processed/` or `processing/`, a vector point) bumps the version and logs the change, even when the manifest held none of it: a writer that stored objects for the entry outside its lock, as batch ingest does, checks the version under the lock and must see that they went.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
      * @summary Reset Entry Processing
      * @param {number} entryId
      * @param {*} [options] Override http request option.
@@ -306,7 +306,7 @@ export interface EntriesApiInterface {
      */
     resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ProcessingResetResponse>>;
     /**
-     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  A reset that deleted anything (a manifest section, an object under `processed/` or `processing/`, a vector point) bumps the version and logs the change, even when the manifest held none of it: a writer that stored objects for the entry outside its lock, as batch ingest does, checks the version under the lock and must see that they went.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
      * Reset Entry Processing
      */
     resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ProcessingResetResponse>;
@@ -450,14 +450,14 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     getEntryApiV1EntriesEntryIdGet(requestParameters: GetEntryApiV1EntriesEntryIdGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<Entry>;
     /**
-     * Get processed content for a single entry
+     * The entry\'s processed content. `text` is always a string when present: the canonical text every offset this API returns indexes into (segment `char_start`/`char_end`, keyword-search snippet `context.offset`). Content stored with `text` as a list of chunks is served with the chunks joined by one space.
      * Get Entry Content
      */
     getEntryContentApiV1EntriesEntryIdContentGetRaw(requestParameters: GetEntryContentApiV1EntriesEntryIdContentGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<{
         [key: string]: any;
     }>>;
     /**
-     * Get processed content for a single entry
+     * The entry\'s processed content. `text` is always a string when present: the canonical text every offset this API returns indexes into (segment `char_start`/`char_end`, keyword-search snippet `context.offset`). Content stored with `text` as a list of chunks is served with the chunks joined by one space.
      * Get Entry Content
      */
     getEntryContentApiV1EntriesEntryIdContentGet(requestParameters: GetEntryContentApiV1EntriesEntryIdContentGetRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<{
@@ -522,12 +522,12 @@ export declare class EntriesApi extends runtime.BaseAPI implements EntriesApiInt
      */
     moveEntryApiV1EntriesEntryIdMovePost(requestParameters: MoveEntryApiV1EntriesEntryIdMovePostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<MoveEntryResponse>;
     /**
-     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  A reset that deleted anything (a manifest section, an object under `processed/` or `processing/`, a vector point) bumps the version and logs the change, even when the manifest held none of it: a writer that stored objects for the entry outside its lock, as batch ingest does, checks the version under the lock and must see that they went.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
      * Reset Entry Processing
      */
     resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<runtime.ApiResponse<ProcessingResetResponse>>;
     /**
-     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  A reset that deleted anything (a manifest section, an object under `processed/` or `processing/`, a vector point) bumps the version and logs the change, even when the manifest held none of it: a writer that stored objects for the entry outside its lock, as batch ingest does, checks the version under the lock and must see that they went.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
      * Reset Entry Processing
      */
     resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost(requestParameters: ResetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRequest, initOverrides?: RequestInit | runtime.InitOverrideFunction): Promise<ProcessingResetResponse>;

package/dist/src/apis/EntriesApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -272,7 +272,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * Get processed content for a single entry
+     * The entry\'s processed content. `text` is always a string when present: the canonical text every offset this API returns indexes into (segment `char_start`/`char_end`, keyword-search snippet `context.offset`). Content stored with `text` as a list of chunks is served with the chunks joined by one space.
      * Get Entry Content
      */
     async getEntryContentApiV1EntriesEntryIdContentGetRaw(requestParameters, initOverrides) {
@@ -290,7 +290,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response);
     }
     /**
-     * Get processed content for a single entry
+     * The entry\'s processed content. `text` is always a string when present: the canonical text every offset this API returns indexes into (segment `char_start`/`char_end`, keyword-search snippet `context.offset`). Content stored with `text` as a list of chunks is served with the chunks joined by one space.
      * Get Entry Content
      */
     async getEntryContentApiV1EntriesEntryIdContentGet(requestParameters, initOverrides) {
@@ -464,7 +464,7 @@ class EntriesApi extends runtime.BaseAPI {
         return await response.value();
     }
     /**
-     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  A reset that deleted anything (a manifest section, an object under `processed/` or `processing/`, a vector point) bumps the version and logs the change, even when the manifest held none of it: a writer that stored objects for the entry outside its lock, as batch ingest does, checks the version under the lock and must see that they went.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
      * Reset Entry Processing
      */
     async resetEntryProcessingApiV1EntriesEntryIdProcessingResetPostRaw(requestParameters, initOverrides) {
@@ -482,7 +482,7 @@ class EntriesApi extends runtime.BaseAPI {
         return new runtime.JSONApiResponse(response, (jsonValue) => (0, index_1.ProcessingResetResponseFromJSON)(jsonValue));
     }
     /**
-     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
+     * Remove everything a processing run derived from an entry, so it can be processed again.  Called by the backend before it re-drives a processing job whose previous attempt failed on infrastructure (a killed worker, a lost heartbeat). Clears, in order: the entry\'s vector points, the objects under its `processed/` and `processing/` prefixes plus every key those two manifest sections registered, and finally the two sections themselves. `original` is never touched. Its keyword-index documents are removed by the keyword-index worker, from a reindex queued in the same transaction.  **The status is never changed.** The processing pool never writes `processing`, and `uploaded` is already the right status for a queued re-run; a reset that rewrote it would race the backend\'s own status bookkeeping. For the same reason a `processed` entry is refused rather than reset: clearing its output under a status that says it is complete would leave a document claiming content it no longer has.  A reset that deleted anything (a manifest section, an object under `processed/` or `processing/`, a vector point) bumps the version and logs the change, even when the manifest held none of it: a writer that stored objects for the entry outside its lock, as batch ingest does, checks the version under the lock and must see that they went.  Idempotent: resetting an entry with nothing derived is a 200 with zero counts and `changed=false`, and does not bump the version. A failure at any store is a 503 that leaves the row untouched, and retrying converges.
      * Reset Entry Processing
      */
     async resetEntryProcessingApiV1EntriesEntryIdProcessingResetPost(requestParameters, initOverrides) {

package/dist/src/apis/HealthApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/HealthApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/PipelinesApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/PipelinesApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SearchApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SearchApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SyncApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/SyncApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WebhooksApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WebhooksApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WeightsApi.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/apis/WeightsApi.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/AdmissionLaneHealth.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/AdmissionLaneHealth.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ArtifactInputConfig.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ArtifactInputConfig.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentRequest.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentRequest.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchContentResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesRequest.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesRequest.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchGetEntriesResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestError.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestError.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestItemResult.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestItemResult.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestOutcome.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestOutcome.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/BatchIngestResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResponse.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResponse.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResult.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/ChunkSearchResult.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/CollectionInfo.d.ts

@@ -2,7 +2,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).

package/dist/src/models/CollectionInfo.js

@@ -5,7 +5,7 @@
  * Client Data API
  * Client Cluster Data API - Manifest-based storage service
  *
- * The version of the OpenAPI document: 2.3.2
+ * The version of the OpenAPI document: 2.6.0
  *
  *
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).