modellerUpdated 2026-05-25

Optional Looker-hosted LookML Workflow

What this covers

This optional path connects Looker Studio to a Looker project generated from a Tessallite model. Choose it only when a compatible Looker instance already exists and reports need LookML modelling hints.

Looker Studio -> Looker connector -> Looker instance
  -> generated LookML -> TLS PostgreSQL gateway :5433 -> Tessallite router

This is not required for Data Studio direct reporting. Generated files and the export workflow are internally tested; execution remains deferred because no licensed Looker instance is available for validation.

Setup

Enable LOOKER_GATEWAY_ENABLED=true and gateway TLS in a controlled validation environment.
In Tessallite select Export then LookML (.zip) for a deployed model.
Commit generated files to a private repository accessible to Looker.
Configure the Looker PostgreSQL-dialect connection to the gateway with SSL required.
Validate in Looker and connect Studio through its Looker connector.

Capture checks

Emitted hint	Validation required
`drill_fields`	Drill action returns correct rows.
`always_filter`	Required filter reaches the gateway query.
`conditionally_filter`	Conditional requirement renders as observed.
`suggest_dimension`	Suggestions render from the declared source.
`access_filter`	Scoped results are enforced without leakage.

Limits

No persistent derived tables against Tessallite, bidirectional LookML import, Looker Action API integration, or certification of Looker-hosted execution is included in version 1. Unsupported symmetric-aggregate window shapes fail rather than executing uncertain results.