Connect your Looker instance to a Dremio database to analyze your
data. This document describes how to set connection parameters in
Looker and configure options to encrypt network traffic.
Looker tests dialect compatibility against
[Dremio](https://www.dremio.com/) version 1.4.9 Enterprise Edition.

## Encrypting network traffic

It is a best practice to encrypt network traffic between the Looker application and your database. Consider one of the options that are described on the [Enabling secure database access](https://docs.cloud.google.com/looker/docs/2614/enabling-secure-db-access.md.txt) documentation page.

## Creating the Looker connection to your database

Follow these steps to create the connection from Looker to your database:

1. In the **Admin** section of Looker, select **Connections** , and then click **Add Connection**.
2. Fill out the connection details. The majority of the settings are common to most database dialects. See the [Connecting Looker to your database](https://docs.cloud.google.com/looker/docs/2614/connecting-to-your-db.md.txt) documentation page for information. Some of the settings are described next. Use the default values in all the other fields, or leave them blank.

   - **Name**: Assign a unique name to the connection. The name is how LookML refers to this connection.
   - **Dialect** : Select **Dremio 11+** or **Dremio**.

     > [!NOTE]
     > **Note:** If you are on a [Looker (Google Cloud core)](https://docs.cloud.google.com/looker/docs/looker-core-overview.md.txt) instance and you don't see your dialect listed in the **Dialect** drop-down menu, see the [Looker (Google Cloud core) documentation](https://docs.cloud.google.com/looker/docs/looker-core-dialects.md.txt#supported_dialects_for) to verify that the dialect is supported for Looker (Google Cloud core) instances.

   - **Host**: Enter the IP address or hostname of the server where Dremio is running.

   - **Port** : The default port is `31010`.

   - **Database** : The default value is `DREMIO`.

   - **Username**: Enter the username that Looker uses to access Dremio.

   - **Password**: Enter the password that is associated with the username that you entered.

   - **Additional JDBC parameters** : Add any additional JDBC parameters. See the [Supported JDBC parameters](https://docs.cloud.google.com/looker/docs/2614/db-config-dremio.md.txt#jdbc-supported) section on this page for the list of parameters that Looker supports.

3. To verify that the connection is successful, click the **Test Connection** button in the **Status details** section at the bottom of the **Connections Settings** page.

4. If Looker displays **Can Connect** , press **Connect** to create the connection.

Your database connection is then added to the list on the Looker [**Connections**](https://docs.cloud.google.com/looker/docs/2614/admin-panel-database-connections.md.txt) **Admin** page.

## Debugging

Connect your web browser to `dremio_host:9047` on the server. From the SQL Editor, run `SELECT 1 FROM (VALUES(1))` to verify that Dremio is installed correctly and that queries are able to execute.

## Supported JDBC parameters

For Dremio, Looker supports the following JDBC parameters in the [**Additional JDBC parameters**](https://docs.cloud.google.com/looker/docs/2614/connecting-to-your-db.md.txt#additional_jdbc_parameters) field for the connection. See the documentation for your database for information on these parameters.

- `disableCertificateVerification`
- `impersonation_target`
- `password`
- `projectId`
- `routing_queue`
- `routing_tag`
- `socksProxyHost`: For public Looker instances, the value for the `socksProxyHost` parameter must be the public IP address of the instance.
- `socksProxyPassword`
- `socksProxyPort`
- `socksProxyUsername`
- `ssl`
- `token_type`
- `user`

## Feature support

For Looker to support some features, your database dialect must also support them.

Dremio supports the following features as of Looker 26.14:

| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | No |
| Symmetric aggregates | No |
| Derived tables | Yes |
| Persistent SQL derived tables | No |
| Persistent native derived tables | No |
| Stable views | No |
| Query killing | Yes |
| SQL-based pivots | No |
| Timezones | Yes |
| SSL | Yes |
| Subtotals | No |
| JDBC additional params | Yes |
| Case sensitive | Yes |
| Location type | Yes |
| List type | No |
| Percentile | No |
| Distinct percentile | No |
| SQL Runner Show Processes | No |
| SQL Runner Describe Table | Yes |
| SQL Runner Show Indexes | No |
| SQL Runner Select 10 | Yes |
| SQL Runner Count | Yes |
| SQL Explain | No |
| OAuth 2.0 credentials | No |
| Context comments | Yes |
| Connection pooling | No |
| HLL sketches | No |
| Aggregate awareness | No |
| Incremental PDTs | No |
| Milliseconds | Yes |
| Microseconds | No |
| Materialized views | No |
| Period-over-period measures | No |
| Approximate count distinct | No |
| In-database analytic models | No |
| Custom calendars | No |

Dremio 11+ supports the following features as of Looker 26.14:

| Feature | Supported? |
|---|---|
| Looker (Google Cloud core) | Yes |
| Symmetric aggregates | Yes |
| Derived tables | Yes |
| Persistent SQL derived tables | No |
| Persistent native derived tables | No |
| Stable views | No |
| Query killing | Yes |
| SQL-based pivots | No |
| Timezones | Yes |
| SSL | Yes |
| Subtotals | No |
| JDBC additional params | Yes |
| Case sensitive | Yes |
| Location type | Yes |
| List type | No |
| Percentile | No |
| Distinct percentile | No |
| SQL Runner Show Processes | No |
| SQL Runner Describe Table | Yes |
| SQL Runner Show Indexes | No |
| SQL Runner Select 10 | Yes |
| SQL Runner Count | Yes |
| SQL Explain | No |
| OAuth 2.0 credentials | No |
| Context comments | Yes |
| Connection pooling | No |
| HLL sketches | No |
| Aggregate awareness | No |
| Incremental PDTs | No |
| Milliseconds | Yes |
| Microseconds | No |
| Materialized views | No |
| Period-over-period measures | No |
| Approximate count distinct | No |
| In-database analytic models | No |
| Custom calendars | No |

## Enabling Dremio Arrow Flight (customer-hosted instances only)

Looker's built-in Dremio dialect doesn't natively support Dremio's Arrow Flight feature. To enable Arrow Flight connections for customer-hosted Looker instances, you can install an Arrow Flight-capable Dremio JDBC driver as a custom JDBC driver.

Follow these steps to enable Arrow Flight in Looker:

1. Download the Dremio Arrow Flight JDBC JAR file from Dremio.
2. Follow the steps on the [Unpackaged JDBC drivers](https://docs.cloud.google.com/looker/docs/2614/unpackaged-jdbc-drivers.md.txt) documentation page to place the JAR file on the server and configure the `custom_jdbc_config.yml` file.
3. In Looker, navigate to **Admin** \> **Databases** \> **Connections**.
4. Edit your Dremio connection or click **Add Connection**.
5. In the **Additional JDBC parameters** field, add the specific parameters that Dremio requires for Arrow Flight, formatted as key-value pairs separated by semicolons (for example, `useFlight=true;`).

## Next steps

After you have completed the database connection, [configure authentication options](https://docs.cloud.google.com/looker/docs/2614/getting-started-with-users.md.txt).