Skip to main content

Bring Your Own OLAP Engine (Live Connector)

Rill supports connecting directly to your own OLAP engine via a "live connector". In this mode, no data is ingested into Rill, and all compute is pushed down to the OLAP engine. Use this mode if you've already handled all of your modeling upstream and want to use Rill as your visual application layer.

Models on Live Connectors

Rill also offers the ability to ingest and create tables directly from a data source to your OLAP engine via the live connector, however you'll need to consider a few topics.

  • Use a test database to avoid accidentally overwriting production data
  • Incremental processing and related queries are not supported
  • Feature availability may vary between different OLAP engines

In order to connect Rill to your OLAP Engine:

  1. Create the connector via the UI
  2. Create the YAML and set the default OLAP engine via the rill.yaml file.
olap_connector in rill.yaml

When setting the OLAP Engine via the UI, the olap_connector key will automatically update the rill.yaml.

OLAP Engines

Rill supports the use of several different OLAP engines to power your dashboards, including:

DuckDB

ClickHouse

MotherDuck

Druid

Pinot

Additional OLAP Engines

Rill is continually evaluating additional OLAP engines that can be added. For a full list of OLAP engines that we support, refer to our OLAP Engines page. If you don't see an OLAP engine that you'd like to use, please don't hesitate to reach out!

Multiple OLAP Engines in a Single Project

Rill supports the use of multiple OLAP engines in a single project with some limitations. For more detailed information, see our reference on multiple OLAP engines. The basic use cases for multiple engines in a single project are:

  1. Using Rill on top of already created and optimized tables from different OLAP sources.
  2. Separating data based on size, as performance on different engines differs based on the size of the data.

Externally Hosted Services

If you have a firewall in front of your externally hosted service, you will need to whitelist the IP addresses below. This will allow you to connect to/from your service once your project is deployed to Rill Cloud.

35.196.245.100
34.74.117.37
35.196.153.31
34.75.22.143
34.148.167.51
35.237.60.193