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. Trino

On this page

  1. Capabilities

Trino

The Trino adapter — connection, write config, metadata, and capabilities.

Capabilities #

CapabilitySupport
ReadsYes
WritesYes — INSERT and external-storage strategies
DDL (create / drop tables)Yes
Metadata introspectionYes

For how writing works across adapters, see Writing.

@lakeql/adapter-trino connects LakeQL to a Trino coordinator. It implements the datasource contract over the Trino REST API and provides the Trino SQL dialect.

Install the adapter:

pnpm add @lakeql/adapter-trino

If you scaffolded with create-app and selected Trino, the adapter is already installed.

Register it in your config:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
import { defineConfig } from "@lakeql/config"
import { trinoAdapterDefinition } from "@lakeql/adapter-trino"

export default defineConfig({
  adapters: [trinoAdapterDefinition],
  dataSources: {
    warehouse: {
      adapter: "trino",
      connection: {
        host: "https://trino.example.com",
        port: 8080,
        catalog: "hive",
        auth: { type: "basic", username: "svc", password: "..." },
      },
    },
  },
})

This section covers the connection, write config, and metadata. The full API reference closes the section. For how a read executes end to end, see data flow.

Connection

Configure the connection to a Trino coordinator.

Write Config

The two writeConfig shapes the Trino adapter supports — INSERT and external storage.

Metadata

How the Trino adapter exposes catalogs, schemas, tables, and columns.

API Reference

Complete reference for the @lakeql/adapter-trino public API.

Previous page

Storage Operations

Next page

Connection