Skip to content

chore(devtools): delete the dag_export bin - #616

Draft
zzylol wants to merge 1 commit into
stack/windows-4-segment-gridfrom
stack/cleanup-1-dag-export-bin
Draft

zzylol wants to merge 1 commit into
stack/windows-4-segment-gridfrom
stack/cleanup-1-dag-export-bin

Conversation

@zzylol

@zzylol zzylol commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Stack: #574 → #620 → #618 → #621 → #627 → #625 → #628 → #632 → #634 → #616 → #617 → #622 → #624 → #629 → #630 → #631 → #633 → #635 → #636 → #637

Problem

The dag_export devtool bin exported query DAGs through the legacy PhysicalPlanCostModel, which the Stage 3 pipeline doesn't use. stage_pipeline now covers inspection. Its tests were the only coverage showing that storage-I/O and hand-off evidence change plan selection. That coverage is tracked in #615 ("Stage 3: evidence-driven cost (storage I/O, hand-off bytes)").

Changes

  • Delete crates/devtools/src/bin/dag_export.rs.
  • docs/user_guide_docs/run-a-query.md: drop the dag_export table rows and the "Export a query DAG" section.
  • docs/develop_docs/storage-operation-costs.md, physical-handoff-costs.md: drop the dag_export --planner-cost-json sentences and the cargo test --bin dag_export verification commands.
  • Fix the stale dag_export comment references in crates/devtools/Cargo.toml and sketch_coverage.rs.

First of a stacked cleanup chain (Q50–Q53).

Test plan

  • cargo fmt --all --check
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo test --workspace: 1665 passed, 0 failed, 13 ignored (after the rebase on main d4869a7; was 1662 passed, 13 ignored)

🤖 Generated with Claude Code

Its export path ran the legacy PhysicalPlanCostModel, which Stage 3 does
not use; stage_pipeline replaces it for inspection. The lost
evidence-changes-selection coverage is tracked in #615.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.

1 participant