Connect to Treasure Data’s Trino (a.k.a. PrestoSQL) using our JDBC Driver.
The Trino JDBC connection has several limitations:
setAutoCommit(false) throws an exception because transactions are not supported.
presto-jdbc queries share the same Presto resources you have available for any other ad hoc or scheduled queries that you submit from the TD Console or through the REST API.
presto-jdbc queries are shown in your account job log, with the exception of the following standard entries:
Query result table
The query result is converted into JSON before being submitted back to separate tools for display. As such, very large result tables may take some time before being displayed. If you have latency problems, contact Support.
Certain BI tools issue “information_schema” requests that cause failed queries in our system. This may be an issue in your tool during first use.
If you see any unexpected errors/bugs/logs that occur during beta use, contact Support.
Our aim is to keep this API up as much as possible. Specifically, we expect to achieve a downtime of less than 1 hour total per month.
For using secure HTTPS (port 443) connection you need to use presto 0.148 or later.
Use the following parameters to connect prestobase on development server:
io.trino.jdbc.TrinoDriver (if you use PrestoSQL Driver, you may use io.prestosql.jdbc.PrestoDriver)
user: (Your TD API key)
password: (dummy string. This value will be ignored)
After presto-jdbc 0.180, because of a bug, a dummy string needs to be set to the password.
Connection URL examples
The connection URL needs to have the following format:
jdbc:trino://api-presto.treasuredata.com:443/td-presto/(database name)?SSL=true Or jdbc:presto://api-presto.treasuredata.com:443/td-presto/(database name)?SSL=true