User Guide Getting Started Help Center Documentation Community Training

Druid support was added in Looker 5.0 using Druid version 0.11.0. This page discusses how to make a Druid connection as well as potential issues and workarounds.

Druid 0.11.0 is required for full Druid compatability. Version 0.10.1 has partial compatability, but has extremely limited functionality.


To kill queries, get the taskId and send a POST request to:


Replace <OVERLORD_IP> and <port> with the IP address and port of your Druid overlord node. The default port is 8090. Consult your database administrator or the Druid documentation for more information.

Configuring Your Druid Database

Enable SQL

To enable SQL on your Druid database, add this line:


to the end of these files:

Optionally, Turn Off Approximation

By default, Druid approximates count distinct. For precise results, add this line:


to the same files:

Database Username

As noted above, Druid 0.11 has no permissions model that uses a username and password, so anyone has full access to the tables. Since you don’t need to create a Druid user to connect from Looker, the username specified for the connection is arbitrary.

Configuring a Connection

  1. In the Admin section of Looker, navigate to the Connections page and click New Connection. Looker displays this page:

    Fill in the fields as follows:

    • Name: The name of the connection. This is how the connection will be referred to in LookML.
    • Dialect: Select Druid.
    • Host:Port: The default port is 8082. (In the screenshot above, we are SSH tunneling to the Druid server, so the host is localhost.) You can also find the IP in your /broker/ file.
    • Database: The name of your database. The Druid database default is druid.
    • Username: Use whatever you like, as described above.
    • Password: Entering a password is optional.
    • Schema: This is the default schema to use when there is no schema specified. Entering a schema is optional.
    • Max Connections: The default is 25.
    • Connection Pool Timeout: The default is 120 seconds.
    • Additional Params: Leave this blank unless you need to customize the JDBC URL options to include useApproximateCountDistinct, useApproximateTopN, or useFallback.

    Warning: Druid’s SQL sqlTimeZone support is not supported by Looker. If you set sqlTimeZone, your results may vary.

  2. Click Test These Settings to verify a connection.

    Looker runs a SELECT 1 query to verify a basic connection and perform a query test. It does not validate that the catalog and schema combination exist or that the user has the required access to that schema.

    If you have any issues, check out our Testing Connections documentation.

  3. Click Add Connection to save these settings.

  4. Test the connection in SQL Runner.

    Navigate to SQL Runner, select your connection and schema, then check if you can see your database tables.

Feature Support

Looker’s ability to provide some features depends on whether the database dialect can support them.

In the current Looker release, Druid supports the following Looker features:

Next Steps

After completing the database connection, configure authentication options.