While it works, the Warehouse Builder writes more than plain text: its answers link every warehouse object it names, and its results come back as KPI cards, charts and diagrams. This page covers that output and what each part means; the builder itself is on The Warehouse Builder.
Every warehouse object and person the builder names in an answer arrives as a link.
After a test, a backfill or a health check, the builder can close its report with a small set of KPI cards: two to four.
The builder draws two kinds of chart: a bar that compares values across groups, such as rows per source system, and a line that follows values over time, such as rows for each day.
The builder keeps to these two kinds; the wider set of blocks a Mind can add is on Charts, KPI cards and diagrams in answers. How a chart or a KPI block is read in the chat, with its table view, zoom and full screen, is on Charts, KPIs and diagrams in chat.
When the point is structure rather than numbers, the builder draws a diagram instead:
One warehouse object: the link carries the object's kind and its number, or its exact name. A workflow link opens the Workflows page on that workflow, and a run link opens the run's diagram.
Tag the person in your message; in a builder chat, @ opens Tag a person. The builder treats a tagged person as your choice: it does not ask who you mean, and it links the person by id rather than writing a name out.
When it reports the outcome of a test, a backfill or a health check. The set holds two to four cards.
The check's own numbers: rows loaded, duplicates, orphans and the source systems that have rows. Each figure comes from the check that ran, so nothing is estimated, and zero is reported as zero.
Two: a bar compares values across groups, such as rows per source system, and a line follows values over time, such as rows for each day.
No. Every figure comes from something the builder read back, such as a check or a count. It reports what it found, zero included.
PK marks a primary key and FK a foreign key; a column that is both carries both marks. A line between two boxes is a foreign-key relationship, and it reads one-to-one, one-to-many or many-to-many.
It can. When the point is how tables relate, it draws an entity relationship diagram to propose the structure, such as a star schema, before it builds.
The diagram could not be read, so the chat shows an error card in place of the drawing. Only that block is affected; ask the builder to send the diagram again if you need it.
No. A builder answer carries links to the objects it names, KPI cards, charts and diagrams, and no document references.