Align silver logical names with pipeline table overrides
This pairing logic assumes every silver table name equals the bronze logical name (bronze name without __cdc), but the pipeline renderer already supports target_table_overrides (see scripts/render-databricks-delta-pipeline.sh), where silver names intentionally differ. In that configuration, silver_by_logical never matches the bronze key, so the new per-table row-count widget splits one logical table into separate bronze-only and silver-only rows with null counts on the opposite side. Use the same override-aware logical mapping when constructing silver_by_logical so overridden pipelines still produce accurate side-by-side counts.
Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #28 (comment)
This pairing logic assumes every silver table name equals the bronze logical name (
bronzename without__cdc), but the pipeline renderer already supportstarget_table_overrides(seescripts/render-databricks-delta-pipeline.sh), where silver names intentionally differ. In that configuration,silver_by_logicalnever matches the bronze key, so the new per-table row-count widget splits one logical table into separate bronze-only and silver-only rows with null counts on the opposite side. Use the same override-aware logical mapping when constructingsilver_by_logicalso overridden pipelines still produce accurate side-by-side counts.Useful? React with 👍 / 👎.
Originally posted by @chatgpt-codex-connector[bot] in #28 (comment)