Presto cluster settings

The following Presto settings should be configured in Qubole console:

Looker settings

In the Admin section of Looker, select Connections, and then select New Connection.

Qubole Presto on AWS and GCP

The Qubole JDBC driver Looker uses to connect with Qubole Presto is on version 2.2.X, which provides support for Qubole Presto hosted on GCP.

In the Admin section of Looker, select Connections, and then select New 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 endpoint for the Qubole connection. See the section Qubole Endpoints for more information.

Qubole Quantum

Qubole Presto Serverless has been rebranded as Qubole Quantum.

In the Admin section of Looker, select Connections, and then select New 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 endpoint for the Qubole connection. See the section Qubole Endpoints for more information.

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:

1. For AWS in the US: endpoint=https://us.qubole.com
2. For GCP in the US: endpoint=https://gcp.qubole.com
3. 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.

In Looker 21.6, Qubole Presto on AWS supports the following Looker features:

In Looker 21.6, Qubole Presto on GCP supports the following Looker features:

In Looker 21.6, Qubole Quantum supports the following Looker features:

Next steps

After you have connected your database to Looker, configure sign-in options for your users.