Skip to content

Automatic translation — the Portuguese version is the reference. View in Portuguese

Updated on 2026-10-04

Trino — connector

Reads the tables of a Trino catalog and schema via the REST protocol (paginated SQL queries) and loads them into the Bronze layer.

On this page (15)

Read first: ../conectores.md (state map) and fichas.md (index of cards).


What it is#

Reads the tables of a Trino catalog and schema via the REST protocol (paginated SQL queries) and loads them into the Bronze layer.

Supported ingestion modes:

  • Nós buscamos — Nós buscamos os dados na sua fonte.

What it's for#

Bring data from Trino into your datalake and make it available to the Bronze/Silver/Gold layers, BI models and the natural language question wizard.

When to use / when not to use#

Use when you need to consolidate this source into the datalake on a scheduled basis, with isolation per workspace.

Remember that the first run with a real credential is followed by our team before the connector is fully released.

Plan and permissions#

  • Plan: core product (connectors are part of all plans; the limit is the number of sources allowed by the plan).
  • Access: requires an active workspace — with a past-due, suspended or canceled subscription, runs are blocked.
  • Shutdown: ingestion runs can be temporarily turned off (maintenance or incident). When that happens, the UI indicates the feature is unavailable at the moment.

Prerequisites#

  • A Trino account with access to the data you want to ingest.
  • Provide the coordinator URL of Trino (https://host:8443), the catalog and schema to read, and a user with SELECT on the tables. With password authentication (requires HTTPS), provide the password — it is encrypted (AES-256-GCM) and never shown again. Without authentication, leave the password blank.

Credentials#

Authentication method: Username and password (or key and secret) using Basic authentication.

Sensitive fields. They are encrypted (AES-256-GCM) and are never kept in the connection config, pipeline definition, export or the DAG. By default the encrypted value is stored in the database; moving this connection's credential to an external credential vault is an explicit choice made per connection after saving — see ../../administracao/credenciais-e-rotacao.md.

  • Password (senha) — Optional: only when the cluster uses password authentication (HTTPS).

Secrets are never re-displayed and are redacted in any error/log (raw token, URL-encoded and in JSON).

Form fields#

FieldLabelTypeRequiredNote
urlServidorCoordinator URLtextyesHTTP(S) address of the Trino coordinator.
catalogoCatalogtextyesCatalog that contains the schema (e.g.: hive, iceberg, postgresql).
schemaSchematextyesdefault: default; Only tables from this schema are listed.
usuarioUsertextyes—
senha 🔒Passwordpassword/secretnosecret (encrypted; external vault optional); Optional: only when the cluster uses password authentication (HTTPS).

Step by step#

  1. In the menu Dados → Conexões, use Nova conexão.
  2. Choose Trino in the catalog.
  3. Fill in the form fields (see the table above).
  4. Use Testar conexão. The result is split into Network (server reachability), Authentication (user and password) and Read (list tables) — each can show OK, Failed, Not applicable or Not tested.
  5. Use Salvar conexão. Saving does NOT start any ingestion.
  6. On the connection card, use Montar extração (or go to Orquestração → Pipelines and use Conectar fonte). The pipeline points to the saved connection — the credential is not copied.
  7. In the review, Publicar (agenda desligada) creates version 1 without executing anything. Afterwards, Ativar agenda and Executar agora are separate actions.

Example — connection test#

Example configuration (all values are fictitious; secrets are masked):

text
# Exemplo sintético (valores fictícios — não são credenciais reais)
urlServidor = <urlServidor>
catalogo = <catalogo>
schema = public
usuario = <usuario>
senha = •••••• (cifrado — nunca exibido)

Expected result#

Testar conexão returns the list of discovered tables/resources. After the first load, the rows appear in your workspace's Bronze layer, ready for the pipeline.

Limits and costs#

  • Pagination: hard cap per run (default 10,000 pages / 5,000,000 rows); anti-loop guard.
  • SaaS load: default batchSize 5,000, maxRows 200,000 per resource.
  • Estimated volume: ~1 GB/month (catalog estimate, not measurement).
  • Cost: the extraction itself is not charged by the platform; the Bronze load consumes datalake processing (billable).

Security#

  • Workspace-scoped: each customer reads and writes only to their own datalake (<prefixo>_bronze / _silver / _gold); there is never leakage between workspaces.
  • Encrypted secrets: sensitive material is encrypted with AES-256-GCM before being stored. The external credential vault is optional and enabled per connection; without it, the encrypted value stays in the database. Changing the value here DOES NOT revoke the credential at the source.
  • Redaction: all errors/logs pass through secret redaction (raw, URL-encoded and in JSON).
  • Production does not mock: a path that would fall into a mock triggers production guard (explicit failure instead of simulating success).

Common errors#

  • Credential rejected (401/403) — the provider did not accept the credential: expired, revoked or missing required permission. Reconnect the source (the source and history are preserved; do not recreate the source).
  • Rate limit (429) — the provider asked to wait. The extraction respects Retry-After and retries; if it repeats, wait and reduce the schedule frequency.
  • Resource not found — check the resource identifier (account, object, report) and the granted permissions.
  • Pagination cursor stuck — the extraction stops when the API cursor does not advance (anti-loop guard). If it happens in consecutive runs, open a support ticket with the connector and resource information.
  • Empty record path — the response arrived without records in the expected location. Check the selected resource and filters (period, account, status) before assuming there is no data.

Troubleshooting#

  • Use Testar conexão to isolate credential/network issues before scheduling.
  • Monitor runs in the connector observability (error rate, p50/p95, freshness).
  • A schema change at the source is signaled by schema drift (new column = info; removed/changed type column = attention).

Related#


Last review: 2026-10-04. Card automatically generated from the product connector catalog.

Related links