Presto cluster settings
The following Presto settings should be configured in Qubole console:
catalog/hive.properties:
hive.metastore-cache-ttl = 0s
hive.metastore-refresh-interval = 5s
hive.allow-rename-table=true
hive.allow-drop-table=true
hive.parquet.use-column-names=true
hive.storage-format=ORC
Looker settings
In the Admin section of Looker, select Connections, and then click Add Connection.
Qubole Presto
The Qubole JDBC driver that Looker uses to connect with Qubole Presto is on version 2.2.X, which provides support for Qubole Presto on Google Cloud, AWS, and Microsoft Azure.
In the Admin section of Looker, select Connections, and then click Add Connection. Fill out the connection details (see the Connecting Looker to your database documentation page for more information):
- Dialect: Enter Qubole Presto.
- Cluster Label: Enter the cluster name from the Qubole Control Panel.
- Database: Enter hive.
- API Key: This is the Looker user's authentication token. If you have enabled Persistent Derived Tables, enter the PDT user's authentication token in the PDT Overrides column.
- Schema: Enter the default schema to use.
- Persistent Derived Tables: Select this box to enable PDTs.
- Temp Database: If PDTs are enabled, set this to a database/schema where the user has full privileges to create, drop, rename, and alter tables.
- Additional Params: Enter any additional JDBC Connection String Properties.
- You must use the Additional Params field to specify the
endpointfor the Qubole connection. See the Qubole endpoints section on this page for more information.
- You must use the Additional Params field to specify the
Qubole Quantum
Qubole Presto Serverless has been rebranded as Qubole Quantum.
In the Admin section of Looker, select Connections, and then click Add Connection. Fill out the connection details (see the Connecting Looker to your database documentation page for more information):
- Dialect: Enter Qubole Quantum.
- Database: Enter hive.
- API Key: This is the Looker user's authentication token. If you have enabled Persistent Derived Tables, enter the PDT user's authentication token in the PDT Overrides column.
- Schema: Enter the default schema to use.
- Persistent Derived Tables: Select this box to enable PDTs.
- Temp Database: If PDTs are enabled, set this to a database/schema where the user has full privileges to create, drop, rename, and alter tables.
- Additional Params: Enter any additional JDBC Connection String Properties.
- You must use the Additional Params field to specify the
endpointfor the Qubole connection. See the Qubole endpoints section on this page for more information.
- You must use the Additional Params field to specify the
For more information about connection settings, see the Connecting Looker to your database documentation page.
Qubole endpoints
By default, the Qubole connections are made to api.qubole.com. Find the appropriate value in Supported Qubole Endpoints for your cloud provider and the geographic region in which your Qubole database is deployed.
Add the parameter endpoint=url_of_endpoint in the Additional Params field of the Connection Settings:
- For AWS in the US:
endpoint=https://us.qubole.com - For Google Cloud in the US:
endpoint=https://gcp.qubole.com - For Azure in the US:
endpoint=https://azure.qubole.com
Feature support
For Looker to support some features, your database dialect must also support them.
Qubole Presto supports the following features as of Looker 23.4:
| Feature | Supported? |
|---|---|
| Support Level | Supported |
| Symmetric Aggregates | Yes |
| Derived Tables | Yes |
| Persistent SQL Derived Tables | Yes |
| Persistent Native Derived Tables | Yes |
| Stable Views | Yes |
| Query Killing | Yes |
| Pivots | Yes |
| Timezones | Yes |
| SSL | Yes |
| Subtotals | Yes |
| JDBC Additional Params | Yes |
| Case Sensitive | Yes |
| Location Type | Yes |
| List Type | Yes |
| Percentile | Yes |
| Distinct Percentile | No |
| SQL Runner Show Processes | Yes |
| SQL Runner Describe Table | Yes |
| SQL Runner Show Indexes | No |
| SQL Runner Select 10 | Yes |
| SQL Runner Count | Yes |
| SQL Explain | Yes |
| Oauth Credentials | No |
| Context Comments | Yes |
| Connection Pooling | No |
| HLL Sketches | No |
| Aggregate Awareness | Yes |
| Incremental PDTs | No |
| Milliseconds | Yes |
| Microseconds | No |
| Materialized Views | No |
| Approximate Count Distinct | Yes |
Next steps
After you have connected your database to Looker, configure sign-in options for your users.