Trino refuses a password over plain HTTP
Measured against a coordinator with authentication switched off, a basic auth header over plain HTTP still answers 401, so the connection is refused early.
6 posts
Writing on Apache Trino
Federated SQL — one query across the catalogs you already have, from object storage to RDBMS. Where it stops: Trino queries catalogs; it does not manage a lakehouse. Writes depend on the underlying connector.
Paging Trino, and the session settings that do not stick
The clause order is transposed for you and a trailing semicolon is a syntax error, while a session setting succeeds and then affects nothing.
Why a Trino diagram draws boxes and never edges
The catalog views a connector could declare a key through do not exist here, so the empty edge set is the engine answer rather than an empty schema.
Monitoring a query engine that stores nothing
Nodes, sessions, slow queries and per-catalog connectors all report, while database size is N/A rather than zero, because there is no storage to measure.
Trino plans are planned, never analyzed
Only the planning form is ever emitted, because the analyze form executes the statement and a plan view reaching object storage twice is a real invoice.
On a Trino connection the database field is a catalog
Pinning a catalog scopes the whole tree two levels deep, and a connection that pins none still connects and runs fully qualified statements with no tree.