trino-duckdb connector

[ashfordm]

Hello!

Set-up trino using helm chart and trying to use duckdb to read parquet files from s3 (minio).

Followed all the steps in https://trino.io/docs/current/connector/duckdb.html

create the file etc/catalog/example.properties.

connector.name=duckdb
connection-url=jdbc:duckdb:

The must point to an existing, persistent DuckDB database file.
For example, use jdbc:duckdb:/opt/duckdb/trino.duckdb for a database created with the command duckdb /opt/duckdb/trino.duckdb.
The database automatically contains the main schema and the information_schema schema. Use the main schema for your new tables or create a new schema.

When using the connector on a Trino cluster the path must be consistent on all nodes and point to a shared storage to ensure that all nodes operate on the same database.

show catalogs;
Catalog

duckdb

show schemas in duckdb;

Query 20250902_151329_00001_f2h64, FAILED, 3 nodes
Splits: 36 total, 0 done (0.00%)
0.07 [0 rows, 0B] [0 rows/s, 0B/s]

Query 20250902_151329_00001_f2h64 failed: Error listing schemas for catalog duckdb: IO Error: Cannot open file "/opt/duckdb/trino.duckdb": No such file or directory

What changes do I make to the values.yaml to make the trino.duckdb available in trino?

Thanks in advance!