From bb75e7b35b5ec700cd24f94c149f543f1b942398 Mon Sep 17 00:00:00 2001 From: dnskr Date: Sat, 8 Nov 2025 23:31:29 +0100 Subject: [PATCH] Fix the table rendering on the Watcher Execution Mode page --- docs/getting_started/watcher-execution-mode.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/getting_started/watcher-execution-mode.rst b/docs/getting_started/watcher-execution-mode.rst index 190fdc2693..b532ac1dbd 100644 --- a/docs/getting_started/watcher-execution-mode.rst +++ b/docs/getting_started/watcher-execution-mode.rst @@ -18,13 +18,13 @@ This provides strong observability and task-level retry control — but it comes Consider the `google/fhir-dbt-analytics `_ project: -+--------------------------------------+----------------------------------+------------------+ -| Run Type | Description | Total Runtime | -+======================================+==================================+==================+ -| Single ``dbt run`` (dbt CLI) | Runs the whole DAG in one command | ~5m 30s | -+--------------------------------------+----------------------------------+------------------+ ++-------------------------------------------------------------+-----------------------------------+------------------+ +| Run Type | Description | Total Runtime | ++=============================================================+===================================+==================+ +| Single ``dbt run`` (dbt CLI) | Runs the whole DAG in one command | ~5m 30s | ++-------------------------------------------------------------+-----------------------------------+------------------+ | One ``dbt run`` per model, totalling 184 commands (dbt CLI) | Each model is its own task | ~32m | -+--------------------------------------+----------------------------------+------------------+ ++-------------------------------------------------------------+-----------------------------------+------------------+ This difference motivated a rethinking of how Cosmos interacts with dbt.