Skip to content

docs: reorganize docs/ and sync materialization flow diagrams with macros - #1627

Merged
sd-db merged 3 commits into
mainfrom
sd-db/docs-reorg
Aug 10, 2026
Merged

docs: reorganize docs/ and sync materialization flow diagrams with macros#1627
sd-db merged 3 commits into
mainfrom
sd-db/docs-reorg

Conversation

@sd-db

@sd-db sd-db commented Aug 9, 2026

Copy link
Copy Markdown
Collaborator

Description

Reorganizes docs/ and brings the materialization flow diagrams back in sync with the current macros.

Structure

  • Split docs/ into docs/flow/ (architecture — the materialization flow diagrams) and docs/guides/ (user-facing how-tos), keeping dbt-databricks-dev.md, testing.md, and dbr-capability-system.md at the top level. Moves preserve history.
  • New docs/README.md (index) and docs/flow/README.md, which explains the use_materialization_v2 behavior flag (defaults to False) that selects between the V1 and V2 diagrams.
  • New flow docs for snapshot, streaming table, and materialized view (previously undocumented).
  • Every doc now carries a _Last updated:_ stamp.

Flow-diagram sync (targeted fixes, verified against the macros)

  • seed V2: removed the transaction split / COMMIT / index creation that create_seed_v2 no longer performs; split the view/MV vs streaming-table compiler errors. seed V1: gated index creation on first-run/full-refresh (seeds.sql).
  • table V2 and incremental "New": removed the fabricated up-front staging-cleanup node.
  • incremental "New": reordered the config-change steps to match apply_config_changeset (tags → tblproperties → liquid → comments → constraints).
  • incremental "Existing": gated liquid clustering inside the config-change branch, matching the macro.
  • table V1, view V1/V2, replace, snapshot, streaming_table, materialized_view: verified accurate, unchanged.

Docs wiring & drift fixes

  • Wired the flow docs into AGENTS.md with a "keep docs in sync, code is the source of truth" note.
  • Fixed the broken README.md link to databricks-workflows.md (+ moved guide paths), updated CONTRIBUTING.MD toxhatch commands, and reconciled the Python 3.93.10 floor.

Testing

Docs-only — no runtime impact. All 8 flow docs' Mermaid diagrams render via mermaid-cli (13 charts); internal links resolve; pre-commit run --all-files passes.

…cros

Restructure docs/ into flow/ (architecture) and guides/ (tutorials):
- Move the 5 flow diagrams into docs/flow/ and the 4 how-to guides into
  docs/guides/ (history preserved via rename).
- Add docs/README.md (index) and docs/flow/README.md, which explains the
  use_materialization_v2 behavior flag that selects the V1/V2 diagrams.
- Add flow docs for snapshot, streaming table, and materialized view.
- Stamp every doc with a "Last updated" date.

Sync the flow diagrams with the current macros (targeted fixes only):
- seed V2: drop the transaction split, COMMIT, and index creation that
  create_seed_v2 no longer performs; split the view/MV vs streaming-table
  errors. seed V1: gate index creation on first-run/full-refresh.
- table V2 and incremental "New": remove the fabricated up-front staging
  cleanup node.
- incremental "New": reorder the config-change steps to match
  apply_config_changeset (tags, tblproperties, liquid, comments, constraints).
- incremental "Existing": gate liquid clustering inside the config-change
  branch, matching the macro.

Wire the flow docs into AGENTS.md with a "keep docs in sync, code is the
source of truth" note. Fix drift outside docs/: README's broken
databricks-workflows.md link and moved guide paths, CONTRIBUTING's tox->hatch
commands, and the Python 3.9->3.10 floor.
@sd-db
sd-db marked this pull request as ready for review August 9, 2026 12:07
@sd-db
sd-db requested a review from jprakash-db as a code owner August 9, 2026 12:07
@sd-db
sd-db merged commit 0eb13d7 into main Aug 10, 2026
1 check passed
@sd-db
sd-db deleted the sd-db/docs-reorg branch August 10, 2026 08:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants