LakeQL
Overview
  • Introduction
  • Datasource Contract
  • API Reference
Writing
  • Write Strategies
  • Load Strategies
  • Partitioning
Storage
  • Storage Operations
Trino
  • Connection
  • Write Config
  • Metadata
  • API Reference
Fabric
  • Connection
  • Metadata
  • API Reference
GitHub
LakeQL
  1. Data Sources
  2. Storage
  3. Storage Operations

On this page

  1. Responsibilities

Storage Operations

Upload, list, and delete operations against object storage.

Storage operations are the narrow interface the external-storage write strategy uses to talk to object storage. They have one responsibility: moving files in and out of storage. They know nothing about load strategies or partitioning.

Responsibilities #

  • Upload — write a serialized file to a storage path.
  • List — enumerate files under a prefix.
  • Delete — remove files, used during cleanup.

Load-strategy semantics (whether to replace, append, or extend) live in the write strategy, not here. The table manager handles the external-table DDL that registers uploaded files. This separation keeps each piece testable on its own. A write strategy can swap the storage backend without touching its load logic.

Storage is only involved in the external-storage write path. The INSERT strategy writes through SQL and does not touch object storage.

Previous page

Storage

Next page

Trino