Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.omni.co/llms.txt

Use this file to discover all available pages before exploring further.

Supported only for Snowflake, Databricks, and BigQuery connections.
This setting allows you to route different job types to different warehouses or BigQuery slot reservations without creating duplicate connections. This is useful for optimizing resource allocation based on workload characteristics - for example, routing AI traffic to a small warehouse while sending scheduled deliveries to a larger one. compute_routing is additive. Existing models that use warehouse_override or slot_reservation continue to work unchanged, as those parameters take precedence over compute_routing. See Resolution precedence for more information.

​
Syntax

compute_routing:
  workbook: "<warehouse_or_reservation_name>"
  dashboard: "<warehouse_or_reservation_name>"
  scheduled: "<warehouse_or_reservation_name>"
  export_download: "<warehouse_or_reservation_name>"
  api_run: "<warehouse_or_reservation_name>"
  suggestions: "<warehouse_or_reservation_name>"
  agentic: "<warehouse_or_reservation_name>"

​
Properties

All keys are optional. Any job type without a routing entry falls through to lower-precedence routing mechanisms or the connection default.
​
compute_routing
object
An object that maps job types to warehouse names (for Snowflake and Databricks) or slot reservation names (for BigQuery).

​
Resolution precedence

When multiple compute routing mechanisms are defined, Omni resolves them in the following order (highest precedence first):
  1. sql_preamble (if it contains warehouse or session commands)
  2. Topic-level warehouse_override or slot_reservation
  3. Model-level warehouse_override or slot_reservation
  4. compute_routing entry for the matching job type
  5. Connection default warehouse or slot reservation
If a model defines both warehouse_override (or slot_reservation) and compute_routing, every query uses warehouse_override and compute_routing has no effect. To use per-job-type routing, omit warehouse_override and slot_reservation from the model.

​
Validation

Omni validates compute_routing when the model is saved. Using compute_routing on a connection other than Snowflake, Databricks, or BigQuery surfaces a model validation error. Omni does not check whether the referenced warehouse or slot reservation exists until query run time. If you reference a warehouse or reservation that doesn’t exist or that the connection user can’t access, queries for that job type fail at run time.

​
Examples

​
Route dashboards and exports to different warehouses

In this example, dashboard queries use DASHBOARD_WH while exports use EXPORT_WH. Other job types fall through to the connection default.

​
Isolate AI workloads to a dedicated warehouse

This configuration routes filter autocomplete suggestions to a small warehouse and AI-triggered traffic (Omni’s AI agents, MCP, and AI context-gathering) to a dedicated agent warehouse.

​
BigQuery slot reservation routing

For BigQuery connections, compute_routing values reference slot reservation names rather than warehouse names.