@gscdump/engine 0.6.1 → 0.6.3

package/dist/entities.d.mts

@@ -1,51 +1,5 @@
+import { a as DataSource } from "./_chunks/storage.mjs";
 import { TenantCtx } from "gscdump/contracts";
-interface DataSource {
-  read: (key: string, range?: {
-    offset: number;
-    length: number;
-  }, signal?: AbortSignal) => Promise<Uint8Array>;
-  write: (key: string, bytes: Uint8Array) => Promise<void>;
-  delete: (keys: string[]) => Promise<void>;
-  /**
-   * One-shot listing under a prefix. Implementations may cap the number of
-   * returned keys (typically 10k) — callers iterating full tenant space
-   * should prefer `streamList` when available or narrow the prefix.
-   */
-  list: (prefix: string) => Promise<string[]>;
-  /**
-   * Per-key URI probe. Returns a URI string DuckDB's `httpfs` (or an
-   * equivalent engine that fetches its own I/O) can read directly, or
-   * `undefined` if the key isn't URI-resolvable on this backend and the
-   * caller must fall back to `read(key)` for the bytes.
-   *
-   * Contracts:
-   * - When defined, the returned URI MUST yield byte-identical content to
-   *   `read(key)`. Callers rely on this for correctness.
-   * - Backends with a native URI for every key (filesystem: absolute path,
-   *   R2 via `httpfs`: signed URL) may always return a string.
-   * - Backends without a native URI shape (in-memory) omit the method or
-   *   return `undefined` per call.
-   * - Mixed-per-query is allowed: some keys in one query may return a URI,
-   *   others may not; the executor branches per key.
-   */
-  uri?: (key: string) => string | undefined;
-  /**
-   * Optional — probe the byte size of a key without reading it. Used by
-   * the engine to fill in `WriteResult.bytes` when a codec reports 0 or
-   * unknown but the file is non-trivial.
-   */
-  head?: (key: string) => Promise<{
-    bytes: number;
-  } | undefined>;
-  /**
-   * Optional streaming variant of `list`. Implementations that page
-   * backing-store results (R2, S3) should implement this and yield keys
-   * lazily. `list` may return up to an adapter-defined cap (typically
-   * 10k keys); callers iterating full tenant space must prefer
-   * `streamList` when available, or chunk by narrower prefixes.
-   */
-  streamList?: (prefix: string) => AsyncIterable<string>;
-}
 /**
  * GSC URL inspection result fields we persist. Mirrors the
  *  `searchconsole_v1.Schema$UrlInspectionResult` shape but as plain JSON