dbt and LookML Integration: Descriptions, Joins, and Full Augmentation Visibility

dbt Descriptions in Schema Explorer

Table and column descriptions from your dbt project now appear directly in the schema explorer, labeled dbt and ranked above warehouse-native descriptions because these are the definitions Orion's agents read when answering your questions.

Interactive Count Tiles on LookML Panel

Count tiles on a data source's LookML panel are now interactive. Select any count to see exactly which views, dimensions, measures, or descriptions are behind it, with anything that did not come across listed first and the findings that explain each gap in the same place.

LookML Joins in Schema Tab

The Schema tab now shows join paths taken from a data source's own LookML for warehouses with a LookML repository connected. Orion uses these declared joins when writing SQL, so it no longer has to guess how tables relate on a warehouse that declares no foreign keys. Each path is marked "declared" because the warehouse has not verified them.

Full Augmentation Inventory

The Augmentation tab now shows exactly what Orion extracted from a connected LookML repository: how many views, dimensions, measures, and descriptions it could match to real warehouse tables, and which ones it could not. Anything Orion cannot match is listed with the file it came from, so you can spot gaps instead of discovering them in an answer. Orion never modifies your LookML.

Column Descriptions from LookML

Column descriptions written in a data source's LookML now appear in Orion for warehouses with a LookML repository connected. Orion uses them when writing SQL, and warehouse-provided descriptions are never replaced.

Improvements

• Context panel now cites dbt and LookML description sources and quotes the descriptions Orion used when answering
• Context panel now shows which file LookML or dbt join definitions came from, displaying the join both ways: the SQL Orion ran and the definition in your file, with direct links to the file
• dbt metadata tools now report what they read to the context panel when Orion explores your dbt project's models, columns, lineage, or declared foreign keys
• Orion now recognizes which columns your LookML declares as primary keys and tracks whether a column description came from LookML or the warehouse
• Long-running conversations and rooms compact context more reliably