Public report — gluten, published 7 Aug 2026. Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version; ask the repo owner for the full report.
Watchdogby Canine Development 07-08-2026 @ 16:27 UTC Public
Code Health Audit

Apache/gluten

No baseline yet — first run coverage not measuredno automated tests
48% Weak
CriticalWeakAdequateStrongExemplary
upper third — near Adequate
Architecture 96% Exemplary Code Health 89% Adequate Maturity 77% Strong Security 47% Weak Readiness 29% Weak

Hobby · weakest lens: Readiness (29%)

Grounded in facts. Every number here is computed, not narrated — reproducible, tool-backed, and traceable to a line of code. How to trust this ▸

33/35dimensions tool-verifieddeterministic · confidence 1.0 · 2 LLM-assisted, advisory
239findings with an exact file:lineof 249 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
35/90dimensions across the health lenses — wide & deep

Executive summary

Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.

apache/gluten carries serious gaps (48%). Several issues below can materially affect correctness, security, or the cost of changing it — and propagate to everything that depends on it.

It is strongest in Architecture (96%) — the structure is clean and changes stay contained. Code Health (89%) is solid too.

The area that most needs attention is Readiness (29%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Security (47%) is the next concern — exposure to security and compliance incidents is elevated.

Leadership focus, highest impact first: 1 No tests found finding(s) in Test Distribution (Test Distribution); ILogger (or Serilog) and log at meaningful points across… (Observability); Keep the changelog current (Release Hygiene).

For scale: Hobby (~0 production lines); rebuilding it from scratch would take roughly ~0.1 person-years (~1 engineer). Approximate, ±~30%.

It builds on a genuinely strong Architecture foundation (96%); the priorities above are the highest-leverage way to bring the rest up to that level.

Code Health 89% Adequate · gated by D4 Architecture 96% ★ Exemplary Maturity 77% Strong Readiness 29% Weak · gated by D9, P2, P6 Security 47% Weak · gated by D29, D36
How the score is built — each lens's share of the headline Width is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
Readiness 29% · 47% weightSecurity 47% · 26% weightMaturity 77% · 14% weightCode Health 89% · 8% weightArchitecture 96% · 4% weight

Raise Readiness 29 → 70 (the Healthy floor) ⇒ headline 48 → ~63.

Code composition — where the lines go
Tests 100%

Top priorities

The highest-leverage moves; the full ranked list is in the Roadmap below.

1
Resolve the 1 No tests found finding(s) in Test Distribution.
+18.8 pts · Low effort · Test Distribution
2
Adopt ILogger (or Serilog) and log at meaningful points across the projects.
+18.8 pts · Medium effort · Observability
3
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
+18.8 pts · Medium effort · Release Hygiene

Diagnosis — what's actually going on

Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: Resolve the 1 No tests found finding(s) in Test Distribution. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ Resolve the 1 No tests found finding(s) in Test Distribution.

At a glance — Code Health · 89% · Adequate · gated by D4

The Good
D1 · .NET / C# Cyclomatic Complexity 8.9 D2 · .NET / C# Cognitive Complexity 7.2 D3 · .NET / C# God Classes 10.0 X1 · Repo Async correctness 10.0 X3 · Repo Exception handling 10.0 X4 · Repo Structured logging 10.0
The Ugly
D4 · .NET / C# Code Duplication 2.0

At a glance — Architecture · 96% · Exemplary

The Good
D7 · .NET / C# Architectural Integrity 10.0 D26 · .NET / C# Project Cohesion 10.0 D27 · .NET / C# Navigability 10.0 D35 · .NET / C# Change Coupling 10.0 AX5 · Repo Architecture & structure 10.0
The Bad
D5 · .NET / C# Coupling 6.9

At a glance — Maturity · 77% · Strong

The Good
D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 10.0 D21 · .NET / C# Naming Consistency 10.0 D34 · .NET / C# Knowledge Freshness 10.0 M1 · Repo Documentation (README) 7.3 M2 · Repo Architecture documentation 8.0 M4 · Repo Documentation accuracy 10.0
The Bad
M3 · Repo Folder & project structure 6.0
The Ugly
D20 · .NET / C# ADR Quality 3.2

At a glance — Readiness · 29% · Weak · gated by D9, P2, P6

The Good
D12 · .NET / C# Dependency Hygiene 10.0 D13 · .NET / C# Secret Scanning 10.0 P1 · Repo CI/CD gates 10.0 P3 · Repo Security & performance tooling 7.0
The Bad
P4 · Repo Deployment & Rollback 5.0
The Ugly
P2 · Repo Observability 0.0 P5 · Repo DR & Backup 4.0 P6 · Repo Release Hygiene 3.0

At a glance — Security · 47% · Weak · gated by D29, D36

The Good
D28 · .NET / C# Secrets (history) 10.0 D31 · .NET / C# IaC & Container Security 8.9
The Ugly
D29 · .NET / C# Static Analysis (SAST) 0.0 D36 · .NET / C# Supply-chain Provenance & Signing 0.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2021 — Injection50High / Critical
A05:2021 — Security Misconfiguration6High / Critical

Roadmap

Begin by addressing the missing test coverage to ensure code reliability. Next, implement structured logging and observability tools to improve system monitoring. Maintain a current changelog for each release to preserve project history. Finally, document disaster recovery procedures and add automated deployment checks to ensure safe releases.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No tests found finding(s) in Test Distribution.+18.8 ptsLowTest Distribution
Adopt ILogger (or Serilog) and log at meaningful points across the projects.+18.8 ptsMediumObservability
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.+18.8 ptsMediumRelease Hygiene
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).+18.1 ptsMediumDR & Backup
Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.+16.6 ptsMediumDeployment & Rollback
Resolve the 50 High finding(s) in Static Analysis (SAST) — start with docker_image.yml (15), build_bundle_package.yml (9), ch_code_style.yml (3).+6.5 ptsMediumStatic Analysis (SAST)
Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing.+1.6 ptsLowSupply-chain Provenance & Signing
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing.+1.6 ptsLowSupply-chain Provenance & Signing

File quality

Per-file score 0–10 — a quality signature. Of 189 files carrying findings, judged against the Production bar: 1% slop · 10% mixed · 89% near-clean.

FileScoreBandWorst signal
cpp-ch/local-engine/docker/image/Dockerfile3.9SlopIaC & Container Security: High IaC: DS-0002
.github/workflows/docker_image.yml4.4MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/build_bundle_package.yml4.4MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/ch_code_style.yml5.1MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/flink.yml5.1MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/pr_bot.yml5.1MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/dependabot.yml5.8MixedStatic Analysis (SAST): High: dependabot-missing-cooldown
.github/workflows/build_release.yml5.8MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/clickhouse_be_trigger.yml5.8MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/cpp_clang_tidy.yml5.8MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/nightly_sync.yml5.8MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/velox_backend_ansi.yml5.8MixedStatic Analysis (SAST): High: run-shell-injection
gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java7.0MixedCode Duplication: Duplicated block (108 lines × 2)
.github/workflows/check_license.yml7.2MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/code_format.yml7.2MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/scala_code_format.yml7.2MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/stale.yml7.2MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
.github/workflows/test_report.yml7.2MixedStatic Analysis (SAST): High: github-actions-mutable-action-tag
gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java7.8MixedCode Duplication: Duplicated block (52 lines × 3)
backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java7.8MixedCode Duplication: Duplicated block (5 lines × 2)

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 33 of 35 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 35 dimensions across the health lenses
D1D2D3D4D5D7D9D12D13D15D16D20D21D26D27D28D29D31D34D35D36AX5M1M2M3M4P1P2P3P4P5P6X1X3X4

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 239 of 249 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
jscpdCode duplication—✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.301✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.301✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 019fdd0c-bc03-7d79-a7af-75471b087a4e.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D18 Solution Shape — evaluation did not complete — Dimension evaluation failed — excluded from the score.
  • D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
  • D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
  • D32 Data Compliance (PII/GDPR) — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
  • D33 JS/npm Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
  • D37 Vulnerability-disclosure Policy — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
  • D38 OSV Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.

Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity (jscpd) — it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (EF migration scaffolds, *.Designer.cs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only; the generated footprint is reported separately under Solution Shape.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

The LLM boundary

LLM-set scores this run (3): D20, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity8.9 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Prevented

8 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ArrowWritableColumnVector.createVectorAccessor at 23.

What to do

  1. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md.

D2 · Cognitive Complexity7.2 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.2 / 10 · rule-coverage 100% · ceiling Prevented

18 method(s) exceeded the cognitive complexity threshold of 15; the worst was ArrowColumnVectorUtils.populatePrimitive at 56.

What to do

  1. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication2.0 / 10Critical✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Verified

32 duplicated block group(s) detected.

Duplicated block (5 lines × 2) · ×4gluten-core/src/main/java/org/apache/gluten/memory/memtarget/DynamicOffHeapSizingMemoryTarget.java:191
Duplicated block (7 lines × 2) · ×2gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:156
Duplicated block (6 lines × 2) · ×2gluten-flink/runtime/src/main/java/org/apache/gluten/velox/VeloxSourceSinkFactory.java:121
Duplicated block (202 lines × 2)gluten-celeborn/src/main/java/org/apache/spark/shuffle/gluten/celeborn/CelebornUtils.java:447
Duplicated block (108 lines × 2)gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1477

+ 22 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with CHShuffleReadStreamFactory.java (2), DynamicOffHeapSizingMemoryTarget.java, NodeSupportVisitor.java. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ArrowColumnVectorUtils.java, ArrowWritableColumnVector.java. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with LocalFilesNode.java, VeloxSourceSinkFactory.java. — One of this dimension's main actionable groups (2 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling6.9 / 10Adequate✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 6.9 / 10 · rule-coverage 100% · ceiling Prevented

0 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

What to do

  1. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d5_recommendation.md.

D7 · Architectural Integrity10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Of 61 mechanizable ADRs, 61 are prevented by analyzers, 0 by tests, 0 exist only in prose. Coverage: 100 %. Cycles found: 0.

✓ On the Gold path — maintain.

Detailed fixes: d7_recommendation.md.

D9 · Test Distribution0.0 / 10Critical✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No test projects found.

No tests found

What to do

  1. Resolve the 1 No tests found finding(s) in Test Distribution. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d9_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 outdated, 0 vulnerable, 0 deprecated packages.

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No source file's living knowledge is concentrated in a single author.

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md.

D20 · ADR Quality / 10Weak◐ Sampled · advisory

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Documented

Evaluated 156 ADR(s) individually; mean quality 3.2/10 (frequently incomplete). 151 flagged with a specific gap.

The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip · ×8backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/20.txt
The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs · ×6backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/10.txt
Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present · ×6backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/11.txt
Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs · ×6backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/12.txt
The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section · ×6backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/13.txt

+ 36 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 8 The body is a physical plan dump (AdaptiveSparkPlan with… finding(s) in ADR Quality — start with 20.txt (8). — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 6 The body is a physical-plan trace showing ShuffleQueryStage and… finding(s) in ADR Quality — start with 10.txt (6). — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 6 Decision and consequences are absent; only a detailed physical-plan… finding(s) in ADR Quality — start with 11.txt (6). — One of this dimension's main actionable groups (6 warning-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency / 10Exemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No projects to assess.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Too little code to assess navigability.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)0.0 / 10Critical✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

252 finding(s): 0 critical, 244 high, 4 medium, 4 low.

High: dependabot-missing-cooldown · ×50.github/dependabot.yml:20detected by semgrep finding

What to do

  1. Resolve the 50 High finding(s) in Static Analysis (SAST) — start with docker_image.yml (15), build_bundle_package.yml (9), ch_code_style.yml (3). — One of this dimension's main actionable groups (50 issue-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security8.9 / 10Strong✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Documented

6 finding(s): 0 critical, 3 high, 0 medium, 3 low.

High IaC: DS-0002 · ×3cpp-ch/local-engine/docker/image/Dockerfiledetected by trivy finding
Low IaC: DS-0005 · ×3cpp-ch/local-engine/docker/image/Dockerfiledetected by trivy finding

What to do

  1. Resolve the 3 High IaC finding(s) in IaC & Container Security — start with Dockerfile (3). — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with Dockerfile (3). — One of this dimension's main actionable groups (3 recommendation-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Every significant source file has living knowledge — recently and meaningfully worked.

✓ On the Gold path — maintain.

Detailed fixes: d34_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling; coupling through a build step, config, or non-source file isn't seen.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

Unpinned build actions
No build provenance
No artifact signing
No SBOM

What to do

  1. Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 No artifact signing finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

M1 · Documentation (README)7.3 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a 'Testing' section to the root README — how to run the test suite.
M2 · Architecture documentation8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

M3 · Folder & project structure6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

  • Projects aren't grouped under a src/ folder — production and tooling code are mixed at the root.
  • Test projects aren't grouped under a tests/ folder — the test surface isn't separable from production code at a glance.

What to do

  • Group production code under src/ (or split deliberately, e.g. backend/ + frontend/) so production and tooling code aren't mixed at the root.
  • Group test projects under tests/ (or test/, spec/) so the test surface is discoverable and CI can scope it.
M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No ILogger/Serilog usage found — production issues will be hard to diagnose.

What to do

  • Adopt ILogger (or Serilog) and log at meaningful points across the projects.
  • Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem/Roslyn scan: CodeQL, Dependabot, secret-scanning, and BenchmarkDotNet presence in pipelines and projects. Exhaustive, deterministic.

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

  • Deployment automation exists but no readiness/liveness probes, rolling-update strategy, lifecycle hooks or migration job were evidenced — a bad release is harder to detect and reverse.

What to do

  • Add readiness/liveness probes and a rolling-update (or blue/green) strategy so a bad release is caught and rolled back automatically.
  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

What to do

  • Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
  • Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
P6 · Release Hygiene3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • A changelog exists but has few versioned entries — keep it current with each release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
  • Stamp a version (csproj <Version>, a VERSION file, or GitVersion) or tag releases with semver so builds and releases are traceable.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X3 · Exception handling10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. Deterministic.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health89%Adequate — gated by D4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture96%ExemplaryStrongest area.
Maturity77%StrongSolid.
Readiness29%Weak — gated by D9, P2, P6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security47%Weak — gated by D29, D36Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 56 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — no DI registrations detected
  • AX10 Code composition — no source files detected — code composition not applicable
  • AX2 Stateful singletons — no singleton implementations detected
  • AX3 Project dependency cycles — no csproj graph available
  • AX4 Dependency direction — no csproj graph available
  • AX6 Interface segregation — no public interfaces
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — no data
  • C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
  • D10 Test Quality — ~19150 lines of test code exist on disk but weren't loaded from the analyzed solution (excluded from the .sln, or co-located/using a test attribute not loaded here), so test quality couldn't be assessed. Include the tests in the analyzed solution to enable this check.
  • D11 Test Reliability — Test reliability not included
  • D14 License Compliance — license scan produced no result — the tool ran but its JSON output could not be parsed; the offline NuGet fallback resolved nothing
  • D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
  • D18 Solution Shape — Dimension evaluation failed
  • D19 Documentation Quality — LLM evaluation failed
  • D22 Internal API Consistency — No exposed public API
  • D23 Boundary Type-Coupling — Zero projects and zero LoC mean the codebase is trivial and has no structure to justify boundaries.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — none of 156 ADRs are conformance-checkable — unverifiable.
  • D30 Dependency Vulnerabilities — No .NET solution found; no NuGet dependencies to scan for vulnerabilities.
  • D32 Data Compliance (PII/GDPR) — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.
  • D33 JS/npm Dependency Vulnerabilities — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D38 OSV Dependency Vulnerabilities — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.
  • D39 IL Efficiency — The target did not build, so no IL was available to measure.
  • D6 Cohesion (LCOM4) — No production classes were analyzable, so cohesion (LCOM4) was not measured (the solution likely failed to load or has no production code).
  • D8 Code Coverage — Coverage not measured — test suite did not build
  • DM1 Domain Modelling — not run — only 1/3 markers (92 value object(s))
  • ED1 Event-Driven — not run — 0/3 markers found
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not run — 0/3 markers found
  • GD1 Unfinished & placeholder code — no source files
  • IC1 Incompleteness & stubs — no C# methods found
  • P12 CI test-gate honesty — no data
  • P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
  • P8 Schema migrations — no EF Core usage detected
  • P9 Domain vs controller coverage — no coverage report found on disk — run tests with `--collect:"XPlat Code Coverage"` (or in CI) to enable this cross-layer check
  • PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF2 Allocation hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
  • S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
  • X2 Cancellation propagation — no async methods found
  • X5 Nullable reference types — no NRT-eligible projects

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Issue — 54 finding(s)
D29 · Static Analysis (SAST) · High · ×50
  • High: dependabot-missing-cooldown .github/dependabot.yml:20 — This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown
  • High: dependabot-missing-cooldown .github/dependabot.yml:26 — This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:46 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:50 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:68 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:74 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:84 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:88 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:93 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: run-shell-injection .github/workflows/build_bundle_package.yml:103 — Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Be sure to use double-quotes the environment variable, like this: "$ENVVAR".
  • High: github-actions-mutable-action-tag .github/workflows/build_bundle_package.yml:107 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_release.yml:28 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/build_release.yml:39 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/ch_code_style.yml:37 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/ch_code_style.yml:39 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/ch_code_style.yml:57 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/check_license.yml:27 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/clickhouse_be_trigger.yml:47 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/clickhouse_be_trigger.yml:52 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/code_format.yml:43 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/cpp_clang_tidy.yml:37 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/cpp_clang_tidy.yml:62 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/docker_image.yml:42 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/docker_image.yml:74 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • High: github-actions-mutable-action-tag .github/workflows/docker_image.yml:98 — GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608`.
  • + 25 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×3
  • High IaC: DS-0002 cpp-ch/local-engine/docker/image/Dockerfile — Image user should not be 'root'
  • High IaC: DS-0021 cpp-ch/local-engine/docker/image/Dockerfile — 'apt-get' missing '-y' to avoid manual input
  • High IaC: DS-0029 cpp-ch/local-engine/docker/image/Dockerfile — 'apt-get' missing '--no-install-recommends'
D18 · Solution Shape · Dimension evaluation failed · ×1
  • Dimension evaluation failed — no .NET solution found at target path
Warning — 186 finding(s)
D20 · ADR Quality · The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip · ×8
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/20.txt
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/20.txt
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/20.txt — Add an Context section explaining why this query structure was chosen and what problem it solves; add a Decision section stating the transformation/optimizer rule applied; and a Consequences section noting any trade-offs (e.g. shuffle cost, memory usage)
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/20.txt — Add an Context section explaining why this query structure was chosen and what problem it solves; add a Decision section stating the transformation/optimizer rule applied; and a Consequences section noting any trade-offs (e.g. shuffle cost, memory usage)
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/20.txt — Add an Context section explaining why this query structure was chosen and what problem it solves; add a Decision section stating the transformation/optimizer rule applied; and a Consequences section noting any trade-offs (e.g. shuffle cost, memory usage)
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/20.txt — Add an Context section explaining why this query structure was chosen and what problem it solves; add a Decision section stating the transformation/optimizer rule applied; and a Consequences section noting any trade-offs (e.g. shuffle cost, memory usage)
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/20.txt — Add an Context section explaining why this query structure was chosen and what problem it solves; add a Decision section stating the transformation/optimizer rule applied; and a Consequences section noting any trade-offs (e.g. shuffle cost, memory usage)
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), revealing no context/problem or explicit decision beneath the scanner clip backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/20.txt — Add an Context section explaining why this query structure was chosen and what problem it solves; add a Decision section stating the transformation/optimizer rule applied; and a Consequences section noting any trade-offs (e.g. shuffle cost, memory usage)
D20 · ADR Quality · The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs · ×6
  • The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/10.txt — Add the problem (e.g. joining on c_custkey#X across two tables) and the decision (pushed filters, in-memory index) along with trade-offs such as batched output ordering and memory cost
  • The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/10.txt — Add the problem (e.g. joining on c_custkey#X across two tables) and the decision (pushed filters, in-memory index) along with trade-offs such as batched output ordering and memory cost
  • The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/10.txt — Add the problem (e.g. joining on c_custkey#X across two tables) and the decision (pushed filters, in-memory index) along with trade-offs such as batched output ordering and memory cost
  • The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/10.txt — Add the problem (e.g. joining on c_custkey#X across two tables) and the decision (pushed filters, in-memory index) along with trade-offs such as batched output ordering and memory cost
  • The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/10.txt — Add the problem (e.g. joining on c_custkey#X across two tables) and the decision (pushed filters, in-memory index) along with trade-offs such as batched output ordering and memory cost
  • The body is a physical-plan trace showing ShuffleQueryStage and BroadcastHashJoin stages with FileSourceScanExecTransformer parquet nodes but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/10.txt — Add the problem (e.g. joining on c_custkey#X across two tables) and the decision (pushed filters, in-memory index) along with trade-offs such as batched output ordering and memory cost
D20 · ADR Quality · Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present · ×6
  • Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/11.txt — Add the decision (e.g. which data source/transform path to use) and its trade-offs (in-memory vs disk cost, shuffle overhead) so consequences are visible
  • Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/11.txt — Add the decision (e.g. which data source/transform path to use) and its trade-offs (in-memory vs disk cost, shuffle overhead) so consequences are visible
  • Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/11.txt — Add the decision (e.g. which data source/transform path to use) and its trade-offs (in-memory vs disk cost, shuffle overhead) so consequences are visible
  • Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/11.txt — Add the decision (e.g. which data source/transform path to use) and its trade-offs (in-memory vs disk cost, shuffle overhead) so consequences are visible
  • Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/11.txt — Add the decision (e.g. which data source/transform path to use) and its trade-offs (in-memory vs disk cost, shuffle overhead) so consequences are visible
  • Decision and consequences are absent; only a detailed physical-plan breakdown with output/columns, batched status, pushed-filters, and scan details is present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/11.txt — Add the decision (e.g. which data source/transform path to use) and its trade-offs (in-memory vs disk cost, shuffle overhead) so consequences are visible
D20 · ADR Quality · Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs · ×6
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/12.txt — Add Context/Problem: why this physical plan was chosen over alternatives, what data it processes, and any constraints (e.g. batched vs streaming). Then state the explicit decision (e.g. use ColumnarBroadcastExchange for left join) and its consequences such as shuffle cost or memory usage.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/12.txt — Add Context/Problem: why this physical plan was chosen over alternatives, what data it processes, and any constraints (e.g. batched vs streaming). Then state the explicit decision (e.g. use ColumnarBroadcastExchange for left join) and its consequences such as shuffle cost or memory usage.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/12.txt — Add Context/Problem: why this physical plan was chosen over alternatives, what data it processes, and any constraints (e.g. batched vs streaming). Then state the explicit decision (e.g. use ColumnarBroadcastExchange for left join) and its consequences such as shuffle cost or memory usage.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/12.txt — Add Context/Problem: why this physical plan was chosen over alternatives, what data it processes, and any constraints (e.g. batched vs streaming). Then state the explicit decision (e.g. use ColumnarBroadcastExchange for left join) and its consequences such as shuffle cost or memory usage.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/12.txt — Add Context/Problem: why this physical plan was chosen over alternatives, what data it processes, and any constraints (e.g. batched vs streaming). Then state the explicit decision (e.g. use ColumnarBroadcastExchange for left join) and its consequences such as shuffle cost or memory usage.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage hierarchies) is a query execution description rather than context/problem or the explicit decision; no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/12.txt — Add Context/Problem: why this physical plan was chosen over alternatives, what data it processes, and any constraints (e.g. batched vs streaming). Then state the explicit decision (e.g. use ColumnarBroadcastExchange for left join) and its consequences such as shuffle cost or memory usage.
D20 · ADR Quality · The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section · ×6
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/13.txt — Add an Context section explaining why this scan order matters (e.g. join/left-side ordering, push-down of IsNotNull filters on a large table), and a Consequences section noting trade-offs such as shuffled hash-aggregation cost vs batched scans
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/13.txt — Add an Context section explaining why this scan order matters (e.g. join/left-side ordering, push-down of IsNotNull filters on a large table), and a Consequences section noting trade-offs such as shuffled hash-aggregation cost vs batched scans
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/13.txt — Add an Context section explaining why this scan order matters (e.g. join/left-side ordering, push-down of IsNotNull filters on a large table), and a Consequences section noting trade-offs such as shuffled hash-aggregation cost vs batched scans
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/13.txt — Add an Context section explaining why this scan order matters (e.g. join/left-side ordering, push-down of IsNotNull filters on a large table), and a Consequences section noting trade-offs such as shuffled hash-aggregation cost vs batched scans
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/13.txt — Add an Context section explaining why this scan order matters (e.g. join/left-side ordering, push-down of IsNotNull filters on a large table), and a Consequences section noting trade-offs such as shuffled hash-aggregation cost vs batched scans
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and Output/Argument annotations) plus one FileSourceScanExecTransformer parquet line for each stage in the plan; there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/13.txt — Add an Context section explaining why this scan order matters (e.g. join/left-side ordering, push-down of IsNotNull filters on a large table), and a Consequences section noting trade-offs such as shuffled hash-aggregation cost vs batched scans
D20 · ADR Quality · The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content · ×6
  • The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/16.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes
  • The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/16.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes
  • The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/16.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes
  • The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/16.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes
  • The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/16.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes
  • The body is a physical-plan dump showing query transformations and scan/transformer details (FileSourceScanExecTransformer parquet, FilterExecTransformer), but no context/problem or explicit decision beneath the plan; only one numbered subsection (1) gives any concrete content backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/16.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes
D20 · ADR Quality · The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences · ×6
  • The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/18.txt — Replace the plan dump with an explicit Context (why shuffle/broadcast joins are needed) and Decision (the transformation/optimizer change being documented) plus Consequences/trade-offs
  • The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/18.txt — Replace the plan dump with an explicit Context (why shuffle/broadcast joins are needed) and Decision (the transformation/optimizer change being documented) plus Consequences/trade-offs
  • The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/18.txt — Replace the plan dump with an explicit Context (why shuffle/broadcast joins are needed) and Decision (the transformation/optimizer change being documented) plus Consequences/trade-offs
  • The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/18.txt — Replace the plan dump with an explicit Context (why shuffle/broadcast joins are needed) and Decision (the transformation/optimizer change being documented) plus Consequences/trade-offs
  • The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/18.txt — Replace the plan dump with an explicit Context (why shuffle/broadcast joins are needed) and Decision (the transformation/optimizer change being documented) plus Consequences/trade-offs
  • The body is a physical-plan dump showing AdaptiveSparkPlan and VeloxColumnarToRow transformations with no context/problem or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/18.txt — Replace the plan dump with an explicit Context (why shuffle/broadcast joins are needed) and Decision (the transformation/optimizer change being documented) plus Consequences/trade-offs
D20 · ADR Quality · The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump · ×6
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/19.txt — Add an explanatory Context section describing why this query/hierarchy was chosen and what it addresses, then document the Decision (e.g. which physical pattern is mandated by the rule), followed by Consequences such as cost/scan-memory trade-offs
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/19.txt — Add an explanatory Context section describing why this query/hierarchy was chosen and what it addresses, then document the Decision (e.g. which physical pattern is mandated by the rule), followed by Consequences such as cost/scan-memory trade-offs
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/19.txt — Add an explanatory Context section describing why this query/hierarchy was chosen and what it addresses, then document the Decision (e.g. which physical pattern is mandated by the rule), followed by Consequences such as cost/scan-memory trade-offs
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/19.txt — Add an explanatory Context section describing why this query/hierarchy was chosen and what it addresses, then document the Decision (e.g. which physical pattern is mandated by the rule), followed by Consequences such as cost/scan-memory trade-offs
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/19.txt — Add an explanatory Context section describing why this query/hierarchy was chosen and what it addresses, then document the Decision (e.g. which physical pattern is mandated by the rule), followed by Consequences such as cost/scan-memory trade-offs
  • The body is a physical-plan representation (AdaptiveSparkPlan with child stages and scan/filter/project transformers) plus output/column metadata for each stage; no context/problem or explicit decision beneath the plan dump backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/19.txt — Add an explanatory Context section describing why this query/hierarchy was chosen and what it addresses, then document the Decision (e.g. which physical pattern is mandated by the rule), followed by Consequences such as cost/scan-memory trade-offs
D20 · ADR Quality · A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text · ×6
  • A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/21.txt — Add a Context section explaining why this query rewrites to a columnar-to-row format (e.g. data size, join pattern), then an explicit Decision stating the transformation path used, and a Consequences section noting trade-offs like shuffle overhead
  • A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/21.txt — Add a Context section explaining why this query rewrites to a columnar-to-row format (e.g. data size, join pattern), then an explicit Decision stating the transformation path used, and a Consequences section noting trade-offs like shuffle overhead
  • A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/21.txt — Add a Context section explaining why this query rewrites to a columnar-to-row format (e.g. data size, join pattern), then an explicit Decision stating the transformation path used, and a Consequences section noting trade-offs like shuffle overhead
  • A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/21.txt — Add a Context section explaining why this query rewrites to a columnar-to-row format (e.g. data size, join pattern), then an explicit Decision stating the transformation path used, and a Consequences section noting trade-offs like shuffle overhead
  • A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/21.txt — Add a Context section explaining why this query rewrites to a columnar-to-row format (e.g. data size, join pattern), then an explicit Decision stating the transformation path used, and a Consequences section noting trade-offs like shuffle overhead
  • A physical plan diagram (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes) is shown but no context/problem or decision statement appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/21.txt — Add a Context section explaining why this query rewrites to a columnar-to-row format (e.g. data size, join pattern), then an explicit Decision stating the transformation path used, and a Consequences section noting trade-offs like shuffle overhead
D20 · ADR Quality · The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away · ×6
  • The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/10.txt — Replace with an actual ADR describing what decision was made, why it matters, and its trade-offs
  • The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/10.txt — Replace with an actual ADR describing what decision was made, why it matters, and its trade-offs
  • The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/10.txt — Replace with an actual ADR describing what decision was made, why it matters, and its trade-offs
  • The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/10.txt — Replace with an actual ADR describing what decision was made, why it matters, and its trade-offs
  • The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/10.txt — Replace with an actual ADR describing what decision was made, why it matters, and its trade-offs
  • The body is a physical plan dump (AdaptiveSparkPlan -> VeloxColumnarToRow -> TakeOrderedAndProjectExecTransformer -> ... ShuffleQueryStage), with no context/problem and no consequences; the title 'Physical Plan' gives nothing away backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/10.txt — Replace with an actual ADR describing what decision was made, why it matters, and its trade-offs
D20 · ADR Quality · The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences · ×6
  • The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/11.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as increased memory usage from ShuffleQueryStages
  • The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/11.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as increased memory usage from ShuffleQueryStages
  • The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/11.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as increased memory usage from ShuffleQueryStages
  • The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/11.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as increased memory usage from ShuffleQueryStages
  • The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/11.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as increased memory usage from ShuffleQueryStages
  • The body is a full physical plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/11.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as increased memory usage from ShuffleQueryStages
D20 · ADR Quality · The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences · ×6
  • The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/16.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as memory pressure from ShuffleQueryStages
  • The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/16.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as memory pressure from ShuffleQueryStages
  • The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/16.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as memory pressure from ShuffleQueryStages
  • The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/16.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as memory pressure from ShuffleQueryStages
  • The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/16.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as memory pressure from ShuffleQueryStages
  • The body is a full physical-plan dump showing AdaptiveSparkPlan and ShuffleQueryStage nodes with no context/problem statement or consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/16.txt — Add the problem (e.g. shuffle cost, join ordering) that drove this plan and note any trade-offs such as memory pressure from ShuffleQueryStages
D20 · ADR Quality · The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision · ×6
  • The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/18.txt — Replace with an ADR describing the problem being addressed by this plan (e.g. data-shape mismatch, shuffle cost) and the concrete decision (change to a columnar format or join order) along with its consequences
  • The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/18.txt — Replace with an ADR describing the problem being addressed by this plan (e.g. data-shape mismatch, shuffle cost) and the concrete decision (change to a columnar format or join order) along with its consequences
  • The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/18.txt — Replace with an ADR describing the problem being addressed by this plan (e.g. data-shape mismatch, shuffle cost) and the concrete decision (change to a columnar format or join order) along with its consequences
  • The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/18.txt — Replace with an ADR describing the problem being addressed by this plan (e.g. data-shape mismatch, shuffle cost) and the concrete decision (change to a columnar format or join order) along with its consequences
  • The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/18.txt — Replace with an ADR describing the problem being addressed by this plan (e.g. data-shape mismatch, shuffle cost) and the concrete decision (change to a columnar format or join order) along with its consequences
  • The body is a physical-plan representation (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), which is diagnostic output rather than context/problem and the explicit decision backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/18.txt — Replace with an ADR describing the problem being addressed by this plan (e.g. data-shape mismatch, shuffle cost) and the concrete decision (change to a columnar format or join order) along with its consequences
D20 · ADR Quality · The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information · ×6
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/21.txt — Replace with an ADR describing the problem being solved (e.g. slow join over parquet tables) and the concrete decision (e.g. switch to a new shuffle/resize/batch plan, add a cost threshold), plus its consequences
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/21.txt — Replace with an ADR describing the problem being solved (e.g. slow join over parquet tables) and the concrete decision (e.g. switch to a new shuffle/resize/batch plan, add a cost threshold), plus its consequences
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/21.txt — Replace with an ADR describing the problem being solved (e.g. slow join over parquet tables) and the concrete decision (e.g. switch to a new shuffle/resize/batch plan, add a cost threshold), plus its consequences
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/21.txt — Replace with an ADR describing the problem being solved (e.g. slow join over parquet tables) and the concrete decision (e.g. switch to a new shuffle/resize/batch plan, add a cost threshold), plus its consequences
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/21.txt — Replace with an ADR describing the problem being solved (e.g. slow join over parquet tables) and the concrete decision (e.g. switch to a new shuffle/resize/batch plan, add a cost threshold), plus its consequences
  • The body is a physical plan dump (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), revealing no context/problem or explicit decision; the title "21" gives no information backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/21.txt — Replace with an ADR describing the problem being solved (e.g. slow join over parquet tables) and the concrete decision (e.g. switch to a new shuffle/resize/batch plan, add a cost threshold), plus its consequences
D20 · ADR Quality · Context/problem and consequences/trade-offs are absent from the visible text · ×4
  • Context/problem and consequences/trade-offs are absent from the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/14.txt — Add a Context section explaining why this physical-plan breakdown matters (e.g. query cost, shuffle behavior), then a Consequences section covering trade-offs like pushed-filter ordering vs join reordering, codegen overhead, and batched scan semantics.
  • Context/problem and consequences/trade-offs are absent from the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/15.txt — Add a Context section explaining why this physical-plan breakdown matters (e.g. query cost, data-shape requirements), then a Consequences section covering trade-offs such as codegen complexity or shuffle overhead
  • Context/problem and consequences/trade-offs are absent from the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/14.txt — Add a Context section explaining why this physical-plan breakdown matters (e.g. query cost, shuffle behavior), then a Consequences section covering trade-offs like pushed-filter ordering vs join reordering, codegen overhead, and batched scan semantics.
  • Context/problem and consequences/trade-offs are absent from the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/15.txt — Add a Context section explaining why this physical-plan breakdown matters (e.g. query cost, data-shape requirements), then a Consequences section covering trade-offs such as codegen complexity or shuffle overhead
D20 · ADR Quality · The body is a full physical plan dump showing query execution (AdaptiveSparkPlan -> VeloxColumnarToRow -> AQEShuffleRead -> ShuffleQueryStage -> ColumnarExchange -> VeloxResizeBatches -> ProjectExecTransformer -> BroadcastHashJoin...), with no context/problem and no consequences; the title "20" gives no signal · ×4
  • The body is a full physical plan dump showing query execution (AdaptiveSparkPlan -> VeloxColumnarToRow -> AQEShuffleRead -> ShuffleQueryStage -> ColumnarExchange -> VeloxResizeBatches -> ProjectExecTransformer -> BroadcastHashJoin...), with no context/problem and no consequences; the title "20" gives no signal backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/20.txt — Add a Context section explaining why this plan was chosen (e.g. data size, join ordering) and a Consequences section noting trade-offs like shuffle cost or memory usage
  • The body is a full physical plan dump showing query execution (AdaptiveSparkPlan -> VeloxColumnarToRow -> AQEShuffleRead -> ShuffleQueryStage -> ColumnarExchange -> VeloxResizeBatches -> ProjectExecTransformer -> BroadcastHashJoin...), with no context/problem and no consequences; the title "20" gives no signal backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/20.txt — Add a Context section explaining why this plan was chosen (e.g. data size, join ordering) and a Consequences section noting trade-offs like shuffle cost or memory usage
  • The body is a full physical plan dump showing query execution (AdaptiveSparkPlan -> VeloxColumnarToRow -> AQEShuffleRead -> ShuffleQueryStage -> ColumnarExchange -> VeloxResizeBatches -> ProjectExecTransformer -> BroadcastHashJoin...), with no context/problem and no consequences; the title "20" gives no signal backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/20.txt — Add a Context section explaining why this plan was chosen (e.g. data size, join ordering) and a Consequences section noting trade-offs like shuffle cost or memory usage
  • The body is a full physical plan dump showing query execution (AdaptiveSparkPlan -> VeloxColumnarToRow -> AQEShuffleRead -> ShuffleQueryStage -> ColumnarExchange -> VeloxResizeBatches -> ProjectExecTransformer -> BroadcastHashJoin...), with no context/problem and no consequences; the title "20" gives no signal backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/20.txt — Add a Context section explaining why this plan was chosen (e.g. data size, join ordering) and a Consequences section noting trade-offs like shuffle cost or memory usage
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×4
  • Duplicated block (5 lines × 2) gluten-core/src/main/java/org/apache/gluten/memory/memtarget/DynamicOffHeapSizingMemoryTarget.java:191 — gluten-core/src/main/java/org/apache/gluten/memory/memtarget/DynamicOffHeapSizingMemoryTarget.java:191-195 | gluten-core/src/main/java/org/apache/gluten/memory/memtarget/DynamicOffHeapSizingMemoryTarget.java:216-220
  • Duplicated block (5 lines × 2) tools/qualification-tool/src/main/java/org/apache/gluten/qt/support/NodeSupportVisitor.java:136 — tools/qualification-tool/src/main/java/org/apache/gluten/qt/support/NodeSupportVisitor.java:136-140 | tools/qualification-tool/src/main/java/org/apache/gluten/qt/support/NodeSupportVisitor.java:142-146
  • Duplicated block (5 lines × 2) backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java:128 — backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java:128-132 | backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java:169-173
  • Duplicated block (5 lines × 2) backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java:151 — backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java:151-155 | backends-clickhouse/src/main/java/org/apache/spark/storage/CHShuffleReadStreamFactory.java:171-175
D20 · ADR Quality · The body is a full physical-plan dump showing every node in a ShuffleQueryStage with input/output and arguments, but no context/problem or explicit decision (the plan itself is the rationale), and consequences/trade-offs are entirely absent · ×3
  • The body is a full physical-plan dump showing every node in a ShuffleQueryStage with input/output and arguments, but no context/problem or explicit decision (the plan itself is the rationale), and consequences/trade-offs are entirely absent backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/17.txt — Replace the physical-plan dump with an explanatory Context section describing why this query shape was chosen and what it solves, then add a Decision section stating the main transformation path and any trade-offs
  • The body is a full physical-plan dump showing every node in a ShuffleQueryStage with input/output and arguments, but no context/problem or explicit decision (the plan itself is the rationale), and consequences/trade-offs are entirely absent backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/17.txt — Replace the physical-plan dump with an explanatory Context section describing why this query shape was chosen and what it solves, then add a Decision section stating the main transformation (e.g. columnar-to-row aggregation) and its purpose, followed by Consequences covering trade-offs like shuffle cost or data movement
  • The body is a full physical-plan dump showing every node in a ShuffleQueryStage with input/output and arguments, but no context/problem or explicit decision (the plan itself is the rationale), and consequences/trade-offs are entirely absent backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/17.txt — Replace the physical-plan dump with an explanatory Context section describing why this query shape was chosen and what it solves, then add a Decision section stating the main transformation (e.g. columnar-to-row aggregation) and its purpose, followed by Consequences covering trade-offs like shuffle cost or data movement
D20 · ADR Quality · Context/problem and consequences/trade-offs are absent (only a detailed physical-plan breakdown with scan/transformer details appears) · ×3
  • Context/problem and consequences/trade-offs are absent (only a detailed physical-plan breakdown with scan/transformer details appears) backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/12.txt — Add a Context section explaining why the parquet scans were moved to InputAdapter/InputIteratorTransformer rather than being pushed down into FilterExec or ProjectExec
  • Context/problem and consequences/trade-offs are absent (only a detailed physical-plan breakdown with scan/transformer details appears) backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/12.txt — Add a Context section explaining why the parquet scans were moved to InputAdapter/InputIteratorTransformer rather than being pushed down into FilterExec or ProjectExec
  • Context/problem and consequences/trade-offs are absent (only a detailed physical-plan breakdown with scan/transformer details appears) backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/12.txt — Add a Context section explaining why the parquet scans were moved to InputAdapter/InputIteratorTransformer rather than being pushed down into FilterExec or ProjectExec
D20 · ADR Quality · The body is a physical-plan dump showing all stages and their children (AdaptiveSparkPlan -> VeloxColumnarToRow -> SortExecTransformer -> InputIteratorTransformer -> ShuffleQueryStage -> Statistics(X) -> ColumnarExchange -> VeloxResizeBatches -> RegularHashAggregateExecTransformer -> ...), with output/column metadata for each stage, but no context/problem statement or consequences/trade-offs · ×3
  • The body is a physical-plan dump showing all stages and their children (AdaptiveSparkPlan -> VeloxColumnarToRow -> SortExecTransformer -> InputIteratorTransformer -> ShuffleQueryStage -> Statistics(X) -> ColumnarExchange -> VeloxResizeBatches -> RegularHashAggregateExecTransformer -> ...), with output/column metadata for each stage, but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/13.txt — Add a Context section explaining why the physical plan is being documented (e.g. query optimization, cost estimation) and a Consequences section on trade-offs such as the high fan-in of ShuffleQueryStage stages
  • The body is a physical-plan dump showing all stages and their children (AdaptiveSparkPlan -> VeloxColumnarToRow -> SortExecTransformer -> InputIteratorTransformer -> ShuffleQueryStage -> Statistics(X) -> ColumnarExchange -> VeloxResizeBatches -> RegularHashAggregateExecTransformer -> ...), with output/column metadata for each stage, but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/13.txt — Add a Context section explaining why the physical plan is being documented (e.g. query optimization, cost estimation) and a Consequences section on trade-offs such as the high fan-in of ShuffleQueryStage stages
  • The body is a physical-plan dump showing all stages and their children (AdaptiveSparkPlan -> VeloxColumnarToRow -> SortExecTransformer -> InputIteratorTransformer -> ShuffleQueryStage -> Statistics(X) -> ColumnarExchange -> VeloxResizeBatches -> RegularHashAggregateExecTransformer -> ...), with output/column metadata for each stage, but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/13.txt — Add a Context section explaining why the physical plan is being documented (e.g. query optimization, cost estimation) and a Consequences section on trade-offs such as the high fan-in of ShuffleQueryStage stages
D20 · ADR Quality · The body is a detailed physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), showing output/columns, pushedfilters, arguments, and the actual data types of each node's input/output. There is no context/problem statement or decision in any form; only an unstructured plan dump appears. · ×3
  • The body is a detailed physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), showing output/columns, pushedfilters, arguments, and the actual data types of each node's input/output. There is no context/problem statement or decision in any form; only an unstructured plan dump appears. backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/14.txt — Add a Context section explaining why this physical-plan structure matters (e.g., join/ordering/scan cost) and a Decision section stating what change was made to arrive at the shown plan, plus Consequences noting trade-offs like increased shuffle or memory usage.
  • The body is a detailed physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), showing output/columns, pushedfilters, arguments, and the actual data types of each node's input/output. There is no context/problem statement or decision in any form; only an unstructured plan dump appears. backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/14.txt — Add a Context section explaining why this physical-plan structure matters (e.g., join/ordering/scan cost) and a Decision section stating what change was made to arrive at the shown plan, plus Consequences noting trade-offs like increased shuffle or memory usage.
  • The body is a detailed physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes), showing output/columns, pushedfilters, arguments, and the actual data types of each node's input/output. There is no context/problem statement or decision in any form; only an unstructured plan dump appears. backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/14.txt — Add a Context section explaining why this physical-plan structure matters (e.g., join/ordering/scan cost) and a Decision section stating what change was made to arrive at the shown plan, plus Consequences noting trade-offs like increased shuffle or memory usage.
D20 · ADR Quality · The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, arguments, and location, but there is no context/problem statement or consequences/trade-offs section · ×3
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, arguments, and location, but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/15.txt — Add an Context/Problem section explaining why the shuffle-based plan was chosen over a simpler one (e.g. join/ordering) and a Consequences section covering trade-offs like memory usage and shuffle overhead
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, arguments, and location, but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/15.txt — Add an Context/Problem section explaining why the shuffle-based plan was chosen over a simpler one (e.g. join/ordering) and a Consequences section covering trade-offs like memory usage and shuffle overhead
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, arguments, and location, but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/15.txt — Add an Context/Problem section explaining why the shuffle-based plan was chosen over a simpler one (e.g. join/ordering) and a Consequences section covering trade-offs like memory usage and shuffle overhead
D20 · ADR Quality · Physical plan with exec-transformer breakdown and output/column metadata is present but there is no context/problem statement (why ShuffleQueryStage or VeloxResizeBatches was chosen over alternatives), no explicit decision, and no consequences/trade-offs · ×3
  • Physical plan with exec-transformer breakdown and output/column metadata is present but there is no context/problem statement (why ShuffleQueryStage or VeloxResizeBatches was chosen over alternatives), no explicit decision, and no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/17.txt — Add a Context section explaining the dataflow bottleneck being addressed (e.g. in-memory shuffle for SortMergeJoin) and an Explicit Decision stating which physical plan is adopted and why; add Consequences noting trade-offs like increased ShuffleQueryStage overhead
  • Physical plan with exec-transformer breakdown and output/column metadata is present but there is no context/problem statement (why ShuffleQueryStage or VeloxResizeBatches was chosen over alternatives), no explicit decision, and no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/17.txt — Add a Context section explaining the dataflow bottleneck being addressed (e.g. in-memory shuffle for SortMergeJoin) and an Explicit Decision stating which physical plan is adopted and why; add Consequences noting trade-offs like increased ShuffleQueryStage overhead
  • Physical plan with exec-transformer breakdown and output/column metadata is present but there is no context/problem statement (why ShuffleQueryStage or VeloxResizeBatches was chosen over alternatives), no explicit decision, and no consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/17.txt — Add a Context section explaining the dataflow bottleneck being addressed (e.g. in-memory shuffle for SortMergeJoin) and an Explicit Decision stating which physical plan is adopted and why; add Consequences noting trade-offs like increased ShuffleQueryStage overhead
D20 · ADR Quality · Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes) is diagnostic output; no context/problem statement or explicit decision describing what the physical reordering accomplishes · ×3
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes) is diagnostic output; no context/problem statement or explicit decision describing what the physical reordering accomplishes backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/19.txt — Add a Context section explaining why ShuffleQueryStage Inner BuildRight was chosen over the original HashAggregate path, and a Decision section stating the reordered plan's purpose (e.g. optimized join on l_shipmode with pushed filters). Consequences could note any performance trade-offs of shuffled joins.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes) is diagnostic output; no context/problem statement or explicit decision describing what the physical reordering accomplishes backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/19.txt — Add a Context section explaining why ShuffleQueryStage Inner BuildRight was chosen over the original HashAggregate path, and a Decision section stating the reordered plan's purpose (e.g. optimized join on l_shipmode with pushed filters). Consequences could note any performance trade-offs of shuffled joins.
  • Physical plan detail (AdaptiveSparkPlan with VeloxColumnarToRow and InputIteratorTransformer nodes) is diagnostic output; no context/problem statement or explicit decision describing what the physical reordering accomplishes backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/19.txt — Add a Context section explaining why ShuffleQueryStage Inner BuildRight was chosen over the original HashAggregate path, and a Decision section stating the reordered plan's purpose (e.g. optimized join on l_shipmode with pushed filters). Consequences could note any performance trade-offs of shuffled joins.
D20 · ADR Quality · Physical plan with execution path and component annotations (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer, VeloxResizeBatches, ColumnarExchange, ShuffleQueryStage) is a diagnostic/optimization tool trace; the ADR's title "12" plus no context/problem and no explicit decision/consequences · ×3
  • Physical plan with execution path and component annotations (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer, VeloxResizeBatches, ColumnarExchange, ShuffleQueryStage) is a diagnostic/optimization tool trace; the ADR's title "12" plus no context/problem and no explicit decision/consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/12.txt — Give this an A rating if it is a physical-plan dump with rationale for each component (why shuffle, why resize batches), but as written it is only a plan listing with no problem statement or consequences. The visible content alone cannot be used.
  • Physical plan with execution path and component annotations (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer, VeloxResizeBatches, ColumnarExchange, ShuffleQueryStage) is a diagnostic/optimization tool trace; the ADR's title "12" plus no context/problem and no explicit decision/consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/12.txt — Give this an A rating if it is a physical-plan dump with rationale for each component (why shuffle, why resize batches), but as written it is only a plan listing with no problem statement or consequences. The visible content alone cannot be used.
  • Physical plan with execution path and component annotations (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer, VeloxResizeBatches, ColumnarExchange, ShuffleQueryStage) is a diagnostic/optimization tool trace; the ADR's title "12" plus no context/problem and no explicit decision/consequences backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/12.txt — Give this an A rating if it is a physical-plan dump with rationale for each component (why shuffle, why resize batches), but as written it is only a plan listing with no problem statement or consequences. The visible content alone cannot be used.
D20 · ADR Quality · The body is a physical-plan dump showing execution trees and metadata (e.g. FileSourceScanExecTransformer parquet with read schema struct<c_custkey · ×3
  • The body is a physical-plan dump showing execution trees and metadata (e.g. FileSourceScanExecTransformer parquet with read schema struct<c_custkey:bigint>), but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/13.txt — Add the problem being addressed (e.g. performance bottleneck, scan order) and the trade-offs of the chosen physical plan (in-memory vs disk-resized batches, shuffle overhead)}
  • The body is a physical-plan dump showing execution trees and metadata (e.g. FileSourceScanExecTransformer parquet with read schema struct<c_custkey:bigint>), but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/13.txt — Add the problem being addressed (e.g. performance bottleneck, scan order) and the trade-offs of the chosen physical plan (in-memory vs disk-resized batches, shuffle overhead)}
  • The body is a physical-plan dump showing execution trees and metadata (e.g. FileSourceScanExecTransformer parquet with read schema struct<c_custkey:bigint>), but no context/problem statement or consequences/trade-offs backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/13.txt — Add the problem being addressed (e.g. performance bottleneck, scan order) and the trade-offs of the chosen physical plan (in-memory vs disk-resized batches, shuffle overhead)}
D20 · ADR Quality · The body is a physical-plan breakdown with input/output/columnar descriptions and codegen/transformer arguments for each node in the query plan (14 nodes), but no context/problem statement or consequences/trade-offs are present · ×3
  • The body is a physical-plan breakdown with input/output/columnar descriptions and codegen/transformer arguments for each node in the query plan (14 nodes), but no context/problem statement or consequences/trade-offs are present backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/14.txt — Add an Context section explaining why this reordering of the hash-aggregate to shuffle join is needed (e.g. better parallelism, memory usage) and a Consequences section noting trade-offs like shuffled ordering and increased shuffle overhead
  • The body is a physical-plan breakdown with input/output/columnar descriptions and codegen/transformer arguments for each node in the query plan (14 nodes), but no context/problem statement or consequences/trade-offs are present backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/14.txt — Add an Context section explaining why this reordering of the hash-aggregate to shuffle join is needed (e.g. better parallelism, memory usage) and a Consequences section noting trade-offs like shuffled ordering and increased shuffle overhead
  • The body is a physical-plan breakdown with input/output/columnar descriptions and codegen/transformer arguments for each node in the query plan (14 nodes), but no context/problem statement or consequences/trade-offs are present backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/14.txt — Add an Context section explaining why this reordering of the hash-aggregate to shuffle join is needed (e.g. better parallelism, memory usage) and a Consequences section noting trade-offs like shuffled ordering and increased shuffle overhead
D20 · ADR Quality · The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, pushed filters, and arguments, but there is no context/problem statement or consequences/trade-offs section · ×3
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, pushed filters, and arguments, but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/15.txt — Add an Context/Problem section explaining why the shuffle-based plan was chosen over a simpler one (e.g. join/ordering) and a Consequences section covering trade-offs like memory usage and shuffle overhead
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, pushed filters, and arguments, but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/15.txt — Add an Context/Problem section explaining why the shuffle-based plan was chosen over a simpler one (e.g. join/ordering) and a Consequences section covering trade-offs like memory usage and shuffle overhead
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with VeloxColumnarToRow and ShuffleQueryStage nodes), showing each ExecTransformer's input/output schema, pushed filters, and arguments, but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/15.txt — Add an Context/Problem section explaining why the shuffle-based plan was chosen over a simpler one (e.g. join/ordering) and a Consequences section covering trade-offs like memory usage and shuffle overhead
D20 · ADR Quality · Physical plan with exec-transformer breakdown and output/column metadata is present but no context/problem or consequences/trade-offs are stated · ×3
  • Physical plan with exec-transformer breakdown and output/column metadata is present but no context/problem or consequences/trade-offs are stated backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/17.txt — Add a Context/Problem section explaining why the ShuffleQueryStage pattern (with its nested ProjectExecTransformer layers) was chosen over alternatives like a single HashAggregate, and a Consequences section noting trade-offs such as shuffle cost and memory usage for large joins
  • Physical plan with exec-transformer breakdown and output/column metadata is present but no context/problem or consequences/trade-offs are stated backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/17.txt — Add a Context/Problem section explaining why the ShuffleQueryStage pattern (with its nested ProjectExecTransformer layers) was chosen over alternatives like a single HashAggregate, and a Consequences section noting trade-offs such as shuffle cost and memory usage for large joins
  • Physical plan with exec-transformer breakdown and output/column metadata is present but no context/problem or consequences/trade-offs are stated backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/17.txt — Add a Context/Problem section explaining why the ShuffleQueryStage pattern (with its nested ProjectExecTransformer layers) was chosen over alternatives like a single HashAggregate, and a Consequences section noting trade-offs such as shuffle cost and memory usage for large joins
D20 · ADR Quality · Context/problem and consequences/trade-offs are absent; only the physical plan (with input/output schema, pushedfilters, and exec-transformer breakdowns) is shown · ×3
  • Context/problem and consequences/trade-offs are absent; only the physical plan (with input/output schema, pushedfilters, and exec-transformer breakdowns) is shown backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/19.txt — Add a Context section explaining why Parquet scans were chosen over in-memory tables and what trade-offs they carry (e.g. shuffle cost, batched vs. streaming behavior). Then document Consequences covering the performance/latency impact of each stage
  • Context/problem and consequences/trade-offs are absent; only the physical plan (with input/output schema, pushedfilters, and exec-transformer breakdowns) is shown backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/19.txt — Add a Context section explaining why Parquet scans were chosen over in-memory tables and what trade-offs they carry (e.g. shuffle cost, batched vs. streaming behavior). Then document Consequences covering the performance/latency impact of each stage
  • Context/problem and consequences/trade-offs are absent; only the physical plan (with input/output schema, pushedfilters, and exec-transformer breakdowns) is shown backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/19.txt — Add a Context section explaining why Parquet scans were chosen over in-memory tables and what trade-offs they carry (e.g. shuffle cost, batched vs. streaming behavior). Then document Consequences covering the performance/latency impact of each stage
D20 · ADR Quality · Physical plan with detailed node definitions and output/column metadata (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer) is a diagnostic/execution trace; no context/problem or explicit decision beneath the plan · ×3
  • Physical plan with detailed node definitions and output/column metadata (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer) is a diagnostic/execution trace; no context/problem or explicit decision beneath the plan backends-velox/src/test/resources/tpch-approved-plan/v1/spark33/22.txt — Add an Context section stating why this physical-plan structure matters (e.g. a join/left-anti pattern over a Parquet scan) and a Decision section naming the transformation/relation change being documented, along with its consequences
  • Physical plan with detailed node definitions and output/column metadata (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer) is a diagnostic/execution trace; no context/problem or explicit decision beneath the plan backends-velox/src/test/resources/tpch-approved-plan/v1/spark34/22.txt — Add an Context section stating why this physical-plan structure matters (e.g. a join/left-anti pattern over a Parquet scan) and a Decision section naming the transformation/relation change being documented, along with its consequences
  • Physical plan with detailed node definitions and output/column metadata (FileSourceScanExecTransformer parquet, FilterExecTransformer, ProjectExecTransformer) is a diagnostic/execution trace; no context/problem or explicit decision beneath the plan backends-velox/src/test/resources/tpch-approved-plan/v1/spark35/22.txt — Add an Context section stating why this physical-plan structure matters (e.g. a join/left-anti pattern over a Parquet scan) and a Decision section naming the transformation/relation change being documented, along with its consequences
D20 · ADR Quality · The body is a physical-plan breakdown with output/column metadata and execution order for VeloxColumnarToRow and ShuffleQueryStage stages; no context/problem statement or consequences/trade-offs are present · ×2
  • The body is a physical-plan breakdown with output/column metadata and execution order for VeloxColumnarToRow and ShuffleQueryStage stages; no context/problem statement or consequences/trade-offs are present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/14.txt — Add the problem being optimized (e.g. large parquet table needing efficient join/aggregate) and the trade-offs of pushing filters vs. in-memory filtering, plus any performance goals that drove this plan selection
  • The body is a physical-plan breakdown with output/column metadata and execution order for VeloxColumnarToRow and ShuffleQueryStage stages; no context/problem statement or consequences/trade-offs are present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark35/14.txt — Add the problem being optimized (e.g. large parquet table needing efficient join/aggregate) and the trade-offs of pushing filters vs. in-memory filtering, plus any performance goals that drove this plan selection
D20 · ADR Quality · The body is a full physical-plan dump showing every node in a query plan plus its arguments and output schema (e.g. FileSourceScanExecTransformer parquet with [c_custkey#X, c_phone#X, c_acctbal#X], FilterExecTransformer with the join condition), but there is no context/problem statement or consequences section · ×2
  • The body is a full physical-plan dump showing every node in a query plan plus its arguments and output schema (e.g. FileSourceScanExecTransformer parquet with [c_custkey#X, c_phone#X, c_acctbal#X], FilterExecTransformer with the join condition), but there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/22.txt — Add a Context/Problem section explaining why this query (or these joins) were chosen and what trade-offs they carry, then a Consequences section covering any performance/memory cost of the plan's batching/pushdown
  • The body is a full physical-plan dump showing every node in a query plan plus its arguments and output schema (e.g. FileSourceScanExecTransformer parquet with [c_custkey#X, c_phone#X, c_acctbal#X], FilterExecTransformer with the join condition), but there is no context/problem statement or consequences section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/22.txt — Add a Context/Problem section explaining why this query (or these joins) were chosen and what trade-offs they carry, then a Consequences section covering any performance/memory cost of the plan's batching/pushdown
D20 · ADR Quality · The body is a physical-plan dump showing all stages and their children with input/output schemas plus push-filter details (stages (1)-(16), output [4], pushedFilters [...] IsNotNull(p_partkey)), but there is no context/problem statement or consequences/trade-offs section · ×2
  • The body is a physical-plan dump showing all stages and their children with input/output schemas plus push-filter details (stages (1)-(16), output [4], pushedFilters [...] IsNotNull(p_partkey)), but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/14.txt — Add an Context/Problem section explaining why the physical plan matters (e.g. a join between l_shipdate and p_partkey on parquet tables) and a Consequences section covering trade-offs such as pushed-filter ordering, codegen cost, and batched vs non-batched behavior
  • The body is a physical-plan dump showing all stages and their children with input/output schemas plus push-filter details (stages (1)-(16), output [4], pushedFilters [...] IsNotNull(p_partkey)), but there is no context/problem statement or consequences/trade-offs section backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/14.txt — Add an Context/Problem section explaining why the physical plan matters (e.g. a join between l_shipdate and p_partkey on parquet tables) and a Consequences section covering trade-offs such as pushed-filter ordering, codegen cost, and batched vs non-batched behavior
D20 · ADR Quality · Context/problem and consequences/trade-offs are absent; only a detailed physical plan with input/output schema and each node's arguments is present · ×2
  • Context/problem and consequences/trade-offs are absent; only a detailed physical plan with input/output schema and each node's arguments is present backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark33/22.txt — Add the problem being solved (e.g. left-anti SortMergeJoin on parquet scan) and the trade-offs of pushing filters to the file source vs filtering in memory, plus any consequences like shuffle cost
  • Context/problem and consequences/trade-offs are absent; only a detailed physical plan with input/output schema and each node's arguments is present backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark35/22.txt — Add the problem being solved (e.g. left-anti SortMergeJoin on parquet scan) and the trade-offs of pushing filters to the file source vs filtering in memory, plus any consequences like shuffle cost
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:156 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:156-162 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:178-184
  • Duplicated block (7 lines × 2) gluten-arrow/src/main/java/org/apache/spark/sql/execution/vectorized/ArrowColumnVectorUtils.java:52 — gluten-arrow/src/main/java/org/apache/spark/sql/execution/vectorized/ArrowColumnVectorUtils.java:52-58 | gluten-arrow/src/main/java/org/apache/spark/sql/execution/vectorized/ArrowColumnVectorUtils.java:87-93
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×2
  • Duplicated block (6 lines × 2) gluten-flink/runtime/src/main/java/org/apache/gluten/velox/VeloxSourceSinkFactory.java:121 — gluten-flink/runtime/src/main/java/org/apache/gluten/velox/VeloxSourceSinkFactory.java:121-126 | gluten-flink/runtime/src/main/java/org/apache/gluten/velox/VeloxSourceSinkFactory.java:135-140
  • Duplicated block (6 lines × 2) gluten-substrait/src/main/java/org/apache/gluten/substrait/rel/LocalFilesNode.java:178 — gluten-substrait/src/main/java/org/apache/gluten/substrait/rel/LocalFilesNode.java:178-183 | gluten-substrait/src/main/java/org/apache/gluten/substrait/rel/LocalFilesNode.java:195-200
D19 · Documentation Quality · LLM evaluation failed · ×1
  • LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[0].suggestion | LineNumber: 0 | BytePositionInLine: 1094.
D20 · ADR Quality · The body is a full physical-plan representation (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes), but no context/problem or decision statement describing what the plan does and why it was chosen; consequences/trade-offs are absent · ×1
  • The body is a full physical-plan representation (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes), but no context/problem or decision statement describing what the plan does and why it was chosen; consequences/trade-offs are absent backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/17.txt — Add an Context section explaining the data source, the query's purpose, and the problem being solved. Add a Decision section stating what this physical plan accomplishes (e.g., computing avg_yearly l_extendedprice per partkey). Conclude with a Consequences section on trade-offs such as shuffle cost or batched scan behavior
D20 · ADR Quality · The body is a full physical-plan representation (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes plus output/column metadata for each node), but no context/problem or explicit decision appears in the visible text · ×1
  • The body is a full physical-plan representation (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes plus output/column metadata for each node), but no context/problem or explicit decision appears in the visible text backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark33/22.txt — Add a Context section explaining why this plan shape was chosen over alternatives, and a Decision section stating what trade-offs are accepted
D20 · ADR Quality · The body is a physical-plan breakdown (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes), showing input/output shapes, arguments, and codegen details for each stage. No context/problem statement or explicit decision appears in the visible text. · ×1
  • The body is a physical-plan breakdown (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes), showing input/output shapes, arguments, and codegen details for each stage. No context/problem statement or explicit decision appears in the visible text. backends-velox/src/test/resources/tpch-approved-plan/v1-bhj-ras/spark34/17.txt — Add an Context section explaining why this plan was chosen over alternatives and a Decision section stating what it accomplishes (e.g., optimized aggregation, shuffled join, batched scan). Consequences/trade-offs could follow.
D20 · ADR Quality · The body is a physical-plan dump showing query transformations and execution plan nodes (AdaptiveSparkPlan, VeloxColumnarToRow, ShuffleQueryStage), with no context/problem statement or decision, only the data flow; consequences/trade-offs are absent · ×1
  • The body is a physical-plan dump showing query transformations and execution plan nodes (AdaptiveSparkPlan, VeloxColumnarToRow, ShuffleQueryStage), with no context/problem statement or decision, only the data flow; consequences/trade-offs are absent backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark33/17.txt — Add an Context section explaining what problem this resolves (e.g. a slow join over parquet tables) and a Decision section stating which plan is adopted and why, plus Consequences covering trade-offs like shuffle cost
D20 · ADR Quality · The body is a full physical-plan dump showing every node in a query plan plus its arguments and output schema (e.g. FileSourceScanExecTransformer parquet with [c_custkey#X, c_phone#X, c_acctbal#X], FilterExecTransformer with the join condition), but no context/problem or consequences/trade-offs are present · ×1
  • The body is a full physical-plan dump showing every node in a query plan plus its arguments and output schema (e.g. FileSourceScanExecTransformer parquet with [c_custkey#X, c_phone#X, c_acctbal#X], FilterExecTransformer with the join condition), but no context/problem or consequences/trade-offs are present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark34/22.txt — Add a Context section explaining why this query is being rewritten (e.g. batched scan vs hash join cost) and a Consequences section on trade-offs like shuffled stages, codegen overhead, and data movement
D20 · ADR Quality · The body is a full physical-plan representation (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes), complete to the point that it would be a Plan document rather than an ADR; no context/problem or consequences are present · ×1
  • The body is a full physical-plan representation (AdaptiveSparkPlan with ShuffleQueryStage and InputIteratorTransformer nodes), complete to the point that it would be a Plan document rather than an ADR; no context/problem or consequences are present backends-velox/src/test/resources/tpch-approved-plan/v1-bhj/spark35/22.txt — Convert this into an ADR by adding Context/Problem (why columnar-to-row conversion is needed) and Consequences/trade-offs (memory cost, shuffle overhead) above the plan dump
D20 · ADR Quality · Context/problem and consequences/trade-offs are absent (only a physical-plan breakdown with input/output schema details appear) · ×1
  • Context/problem and consequences/trade-offs are absent (only a physical-plan breakdown with input/output schema details appear) backends-velox/src/test/resources/tpch-approved-plan/v1-ras/spark34/22.txt — Add a Context section explaining why the parquet scan was moved to the left anti join and the cost of pushing filters vs. moving it
D36 · Supply-chain Provenance & Signing · Unpinned build actions · ×1
  • Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity.
D4 · Code Duplication · Duplicated block (202 lines × 2) · ×1
  • Duplicated block (202 lines × 2) gluten-celeborn/src/main/java/org/apache/spark/shuffle/gluten/celeborn/CelebornUtils.java:447 — gluten-celeborn/src/main/java/org/apache/spark/shuffle/gluten/celeborn/CelebornUtils.java:447-648 | gluten-celeborn/src/main/java/org/apache/spark/shuffle/gluten/celeborn/CelebornUtils.java:708-597
D4 · Code Duplication · Duplicated block (108 lines × 2) · ×1
  • Duplicated block (108 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1477 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1477-1551 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1697-1804
D4 · Code Duplication · Duplicated block (104 lines × 2) · ×1
  • Duplicated block (104 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1639 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1639-1742 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2045-2077
D4 · Code Duplication · Duplicated block (103 lines × 2) · ×1
  • Duplicated block (103 lines × 2) shims/spark35/src/main/java/org/apache/spark/sql/execution/vectorized/WritableColumnVectorShim.java:75 — shims/spark35/src/main/java/org/apache/spark/sql/execution/vectorized/WritableColumnVectorShim.java:75-45 | shims/spark35/src/main/java/org/apache/spark/sql/execution/vectorized/WritableColumnVectorShim.java:78-180
D4 · Code Duplication · Duplicated block (82 lines × 5) · ×1
  • Duplicated block (82 lines × 5) backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsStep.java:70 — backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsStep.java:70-151 | backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsStep.java:158-119 | backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsStep.java:166-143 | backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsStep.java:174-103 | backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsStep.java:182-95
D4 · Code Duplication · Duplicated block (81 lines × 2) · ×1
  • Duplicated block (81 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/columnarbatch/PlaceholderVector.java:35 — gluten-arrow/src/main/java/org/apache/gluten/columnarbatch/PlaceholderVector.java:35-115 | gluten-arrow/src/main/java/org/apache/gluten/columnarbatch/PlaceholderVector.java:116-75
D4 · Code Duplication · Duplicated block (80 lines × 2) · ×1
  • Duplicated block (80 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/columnarbatch/IndicatorVectorBase.java:55 — gluten-arrow/src/main/java/org/apache/gluten/columnarbatch/IndicatorVectorBase.java:55-134 | gluten-arrow/src/main/java/org/apache/gluten/columnarbatch/IndicatorVectorBase.java:135-94
D4 · Code Duplication · Duplicated block (64 lines × 2) · ×1
  • Duplicated block (64 lines × 2) backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsData.java:48 — backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsData.java:48-111 | backends-clickhouse/src/main/java/org/apache/gluten/metrics/MetricsData.java:128-1
D4 · Code Duplication · Duplicated block (59 lines × 18) · ×1
  • Duplicated block (59 lines × 18) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:807 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:807-865 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:871-821 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:875-809 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:879-813 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:883-817 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1296-1342 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1352-1370 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1372-1390 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1392-1354 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1396-1358 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1400-1362 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1404-1366 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1408-1394 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1412-1398 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1416-1402 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1420-1406 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1424-1430 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1436-1418
D4 · Code Duplication · Duplicated block (52 lines × 3) · ×1
  • Duplicated block (52 lines × 3) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:276 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:276-327 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:336-387 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:421-472
D4 · Code Duplication · Duplicated block (42 lines × 2) · ×1
  • Duplicated block (42 lines × 2) gluten-arrow/src/main/java/org/apache/spark/sql/execution/unsafe/UnsafeByteArray.java:61 — gluten-arrow/src/main/java/org/apache/spark/sql/execution/unsafe/UnsafeByteArray.java:61-80 | gluten-arrow/src/main/java/org/apache/spark/sql/execution/unsafe/UnsafeByteArray.java:86-127
D4 · Code Duplication · Duplicated block (40 lines × 2) · ×1
  • Duplicated block (40 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1034 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1034-1073 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:1118-1127
D4 · Code Duplication · Duplicated block (33 lines × 3) · ×1
  • Duplicated block (33 lines × 3) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:220 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:220-252 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:260-244 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowColumnVector.java:264-248
D4 · Code Duplication · Duplicated block (31 lines × 2) · ×1
  • Duplicated block (31 lines × 2) gluten-flink/runtime/src/main/java/org/apache/gluten/client/OffloadedJobGraphGenerator.java:523 — gluten-flink/runtime/src/main/java/org/apache/gluten/client/OffloadedJobGraphGenerator.java:523-553 | gluten-flink/runtime/src/main/java/org/apache/gluten/client/OffloadedJobGraphGenerator.java:572-439
D4 · Code Duplication · Duplicated block (27 lines × 2) · ×1
  • Duplicated block (27 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2014 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2014-2040 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2057-2083
D4 · Code Duplication · Duplicated block (25 lines × 2) · ×1
  • Duplicated block (25 lines × 2) gluten-flink/runtime/src/main/java/org/apache/gluten/util/VectorOutputBridge.java:109 — gluten-flink/runtime/src/main/java/org/apache/gluten/util/VectorOutputBridge.java:109-133 | gluten-flink/runtime/src/main/java/org/apache/gluten/util/VectorOutputBridge.java:139-153
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) gluten-flink/planner/src/main/java/org/apache/gluten/rexnode/functions/BasicCompareOperatorConverters.java:44 — gluten-flink/planner/src/main/java/org/apache/gluten/rexnode/functions/BasicCompareOperatorConverters.java:44-59 | gluten-flink/planner/src/main/java/org/apache/gluten/rexnode/functions/BasicCompareOperatorConverters.java:75-94
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×1
  • Duplicated block (18 lines × 2) backends-clickhouse/src/main/java/org/apache/gluten/vectorized/CHNativeExpressionEvaluator.java:75 — backends-clickhouse/src/main/java/org/apache/gluten/vectorized/CHNativeExpressionEvaluator.java:75-92 | backends-clickhouse/src/main/java/org/apache/gluten/vectorized/CHNativeExpressionEvaluator.java:104-74
D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1
  • Duplicated block (16 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:167 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:167-182 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:780-160
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2179 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2179-2191 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2193-2200
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×1
  • Duplicated block (11 lines × 4) backends-velox/src/main/java/org/apache/gluten/metrics/OperatorMetrics.java:116 — backends-velox/src/main/java/org/apache/gluten/metrics/OperatorMetrics.java:116-126 | backends-velox/src/main/java/org/apache/gluten/metrics/OperatorMetrics.java:127-137 | backends-velox/src/main/java/org/apache/gluten/metrics/OperatorMetrics.java:138-148 | backends-velox/src/main/java/org/apache/gluten/metrics/OperatorMetrics.java:149-159
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2129 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2129-2138 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2139-2108
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×1
  • Duplicated block (8 lines × 2) gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2239 — gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2239-2245 | gluten-arrow/src/main/java/org/apache/gluten/vectorized/ArrowWritableColumnVector.java:2252-2259
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×1
  • Duplicated block (6 lines × 4) gluten-substrait/src/main/java/org/apache/gluten/test/TestStats.java:120 — gluten-substrait/src/main/java/org/apache/gluten/test/TestStats.java:120-125 | gluten-substrait/src/main/java/org/apache/gluten/test/TestStats.java:130-135 | gluten-substrait/src/main/java/org/apache/gluten/test/TestStats.java:163-168 | gluten-substrait/src/main/java/org/apache/gluten/test/TestStats.java:183-188
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — test suite did not build — Coverage NOT MEASURED: the repo's own test suite did not build (a C#/MSBuild compiler error in the test code), so no coverage could be collected. It is excluded from the score rather than counted as a near-zero defect. Fix the test build, or commit the Cobertura/OpenCover/lcov report your CI already produces, and real coverage will be measured.
Recommendation — 8 finding(s)
D31 · IaC & Container Security · Low IaC · ×3
  • Low IaC: DS-0005 cpp-ch/local-engine/docker/image/Dockerfile — ADD instead of COPY
  • Low IaC: DS-0014 cpp-ch/local-engine/docker/image/Dockerfile — RUN using 'wget' and 'curl'
  • Low IaC: DS-0026 cpp-ch/local-engine/docker/image/Dockerfile — No HEALTHCHECK defined
D11 · Test Reliability · Test reliability not included · ×1
  • Test reliability not included — No test projects found, so reliability couldn't be assessed.
D36 · Supply-chain Provenance & Signing · No build provenance · ×1
  • No build provenance — No SLSA provenance generation or build attestation found in CI (e.g. slsa-github-generator, actions/attest-build-provenance).
D36 · Supply-chain Provenance & Signing · No artifact signing · ×1
  • No artifact signing — No artifact signing found in CI (e.g. cosign / sigstore / gitsign).
D36 · Supply-chain Provenance & Signing · No SBOM · ×1
  • No SBOM — No SBOM generation or committed SBOM found (e.g. syft / anchore/sbom-action / *.spdx.json / *.cdx.json).
D9 · Test Distribution · No tests found · ×1
  • No tests found — No test projects found in the repository.
Info — 1 finding(s)
D22 · Internal API Consistency · No exposed public API · ×1
  • No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --report-format json --report-path /dev/stdout --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --json --quiet --timeout 0 --metrics off .252artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesdotnet (no .NET solution)—dotnet (no .NET solution): not present in this environment0—
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .6artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No PII/GDPR ruleset is bundled (the public p/gdpr semgrep pack was retired) — data compliance is not assessed in this scan.0—
D33 · JS/npm Dependency Vulnerabilitiestrivy—trivy: not applicable — No JS/npm manifest or lockfile found outside bin/obj (package.json, package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); no JS dependencies to scan.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md, .github/SECURITY.md, docs/SECURITY.md, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D38 · OSV Dependency Vulnerabilitiesosv-scanner—osv-scanner: not applicable — No JS/npm lockfile found outside bin/obj (package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb); nothing for OSV to scan.0—

Run 019fdd0c-bc03-7d79-a7af-75471b087a4e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 54 · Warnings: 186 · Recommendations: 8 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 07-08-2026 @ 16:27 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md