Skip to content

Connections

A connection gives Riff BI read-only access to one warehouse. Data models are built on top of a connection. Administrators add connections; Modelers can see and browse them.

  1. Go to Connections and click New connection.
  2. Pick the Warehouse type and give the connection a Name people will recognise.
  3. Fill in the fields for that warehouse (see the table below), then click Create connection.
  4. On the connections list, click Test on its row. A successful test shows Connected; otherwise you’ll see what went wrong.
WarehouseWhat you’ll need
PostgreSQLHost, port (5432), database, default schema, username, password, TLS mode
Amazon RedshiftHost, port (5439), database, default schema, username, password (always encrypted)
SnowflakeAccount, database, default schema, warehouse, role, username, and a password or key pair (PKCS#8 PEM private key)
BigQueryProject ID, location, default dataset, an optional cost cap (GB per query), and a service account key (JSON). Grant it BigQuery Data Viewer and Job User only.
DatabricksServer hostname, HTTP path, catalog, default schema, access token
TrinoHost, port (443), catalog, default schema, username, HTTPS or HTTP, and a password, JWT or no authentication
Amazon AthenaRegion, work group, query result location, data catalog, database, and an access key or the server’s own credentials
MySQL / MariaDBHost, port (3306), database, username, password, TLS mode
ClickHouseHost, port (8443), database, username, password, HTTPS or HTTP
MotherDuckDatabase, default schema, access token
Use a read-only account

Riff BI only runs read-only queries, but it’s still good practice to connect with a warehouse user that can only read the schemas you plan to model.

Hosts that may be refused

For safety, Riff BI refuses hosts that point at cloud metadata addresses. Depending on how your Riff BI server is set up, it may also refuse private or internal network addresses (such as 10.x.x.x or localhost). If a test says a host isn’t allowed, ask whoever runs your Riff BI server.

Passwords, keys and tokens are stored encrypted and never shown again after you save. To change one, edit the connection and type the new value. Deleting a connection asks you to confirm first.

Open a connection to see everything it can reach.

  • Schema (left): schemas and tables, with each column’s type. Pick a table to look inside it.
  • Data: the table’s rows. Search, filter and sort without writing a query. Rows load page by page from the warehouse.
  • Query editor: for trying queries by hand. It’s meant for engineers checking data. It reads the warehouse directly, without the data model’s definitions.
  • Changes: what changed in the warehouse since the last check, and what it affects. See Warehouse changes.

Warehouses change under you: a column is dropped, a table is renamed, a permission is taken away. Riff BI notices, and tells you which published models and dashboards are affected, before someone finds a broken chart. Open a connection and choose its Changes tab. Modelers and administrators can read it; only administrators can start a check or change the schedule.

A check reads the warehouse’s table and column list (never your rows) for the tables your published models use, and compares it with the last complete check. Nothing in the warehouse is changed.

  1. Click Check for changes. The strip at the top reads Checking… while it runs.
  2. The first check only saves a baseline. It reports Baseline saved and no changes, because there is nothing yet to compare with. Changes show from the next check.
  3. After that, each check says what it found: Up to date, or a count of changes, listed by table.
A check never says “all clear” when it couldn’t look

If a check couldn’t finish, the strip says Last check couldn’t finish and why in plain words. If it couldn’t read every schema, it says Partly checked and names what it missed (Details lists each schema as read, partly read or not read). Neither one ever reads as up to date.

Each row names the table (and column), what happened, and how sure Riff BI is.

You’ll seeWhat it means
RemovedA table or column is gone.
No longer visibleThe warehouse stopped showing it. It could be removed, or your connection could have lost access. Riff BI can’t tell the two apart, so it doesn’t say “deleted”.
AddedA new table or column appeared. Nothing published uses it yet.
Possibly renamedOne thing went and a similar one appeared. It’s a guess, so it’s marked Likely or Unsure.
Type changed, Type detail changedA column’s data type moved to another kind (text to number), or kept its kind but changed in detail (a length or precision).
Kind changed, View definition changedA table became a view or the reverse, or a view’s definition changed.

The word beside each change is its confidence: Certain (the warehouse showed it directly), Likely or Unsure. A change that was undone (a column that came back) moves to Done, marked Back to how it was. Search narrows the list by table or column.

Click a change to open its detail: the facts, then one card for each published model it touches. A card says how it reaches the model and what depends on it.

  • Will break or Likely to break: a field, measure or chart reads the removed or retyped column.
  • Numbers may change or May change: the field still works, but its result could differ.
  • Unlikely to matter and Nothing uses it: no published model reads it.

Each card lists the model’s fields, measures and the dashboards that use them, with links. The version is shown (“Found against Version 3; the published model is now Version 4”) so a change you’ve already fixed isn’t mistaken for a live one. Only what you’re allowed to see is named. Dashboards and models you can’t open are counted (“2 dashboards you can’t see”), and the detail never claims “nothing uses this” when something hidden might.

On the model builder, a published model whose warehouse changed shows a one-line notice under its header (“The warehouse changed under this model: 1 column removed”) with See changes. Dismiss it and it stays away until something new is found.

The Changes tab sorts what it found into three groups: To do (something your published models use is affected), For your info (new columns, small type changes, things nothing uses) and Done. It opens on To do; when that’s empty it says Nothing needs fixing. A change is only ever Done because Riff BI checked it, never because someone clicked a button.

  1. On a change that has one model left to fix, click Fix… right on its row; otherwise open the change under To do. Each model it touches shows one Suggested fix, for example Use total_amount instead, with what keeps working.
  2. Click Fix… (on the row or in the change). The review lists each change with its fix; you can untick one or choose another option. It shows which charts will break, and says Checked against the warehouse when the fix was tried on the real tables.
  3. Click Publish fix. The fix goes out as a new version on top of what’s published now, without publishing your other unfinished edits, and your draft gets the same fix. If it would leave a chart broken, tick the acknowledgement and use Publish anyway.
  4. Or choose Add to draft instead to publish it yourself later. The change stays in To do, marked Fix in draft, until a published version is fixed.

You need to be able to edit the model to see fixes, and to publish it to publish one. Someone who can edit the model can also Dismiss a change (Expected change, Doesn’t affect us or Being fixed in the warehouse, with an optional note). It comes back, saying why, if it starts affecting something new; Undo brings it back yourself.

On the model builder, the notice’s Fix… opens the same review for every change on that model. Where Rivo is switched on, Ask Rivo opens it with the change attached and “Fix this warehouse change” typed for you to send. Rivo drafts a fix and says how many changes it settles; you review and publish it from its card. It never publishes, and it only says a change is fixed after you have.

While a fix is in the draft, a broken chart tells everyone who sees it A fix is being worked on; otherwise it says The people who look after this data have been told.

Next to the strip, Schedule shows when the next automatic check is due. Administrators open it to choose:

  • Check automatically: on or off for this connection.
  • How often: every hour, 6 hours, 12 hours, day or week. Server default follows the setting your Riff BI server uses (a day, unless your operator changed it).

Automatic checks run only when your Riff BI server has its scheduler switched on. If it doesn’t, the line says Automatic checks aren’t running on this server and you press Check for changes yourself. A check that fails is retried within half an hour, not after a full day.

If a chart on a published model fails because a column or table is gone, or access was lost, Riff BI starts a check on its own (at most one every 15 minutes per connection). The chart shows the same error as before, with a line saying Something changed in the data source. It doesn’t say what: lost access looks the same as a dropped column until the check finishes. The check’s history reads After a chart failed to load, and if nothing changed in the warehouse it says so. This is on for PostgreSQL and MotherDuck; for other warehouses press Check for changes.

Show history lists each check: when, what started it (Manual, Scheduled or after a chart failed), and what it found. Pick one to show only its changes.

The bell in the sidebar footer shows a dot when something is new. Open it to see the latest notes, each linking to the connection’s Changes tab. You’re told when a check finds new changes that reach a published model: administrators are told about any, and the person who created an affected model is told about theirs. You’re also told when a fix is published for a change, and when a publish brings a change you dismissed back to your list, in both cases unless you did it yourself. Opening a note marks it read; Mark all read clears the rest. A note gives the connection and a count, never a model or column name.

The bell checks for news every few minutes (your operator sets how often) and when you return to the tab, so a new note can take a few minutes to appear. There is no email yet.

An operator can switch warehouse change detection off for a whole workspace. When it’s off there’s no Changes tab, no model notice and no checks.