statistics

DE//AGENT currently lists 2 resources under statistics: 2 tutorials. Everything below is derived from the live registry — counts, capabilities, verification state and security posture come from the curated records, never from marketing copy.

Documented learning objectives across these resources:

• Name the parts of a Parquet file — row groups, column chunks, pages, statistics — via Open the Parquet file — row groups, pages, encodings
• Explain what per-row-group statistics buy a reader through predicate pushdown — via Open the Parquet file — row groups, pages, encodings
• Reach the authoritative wording instead of paraphrasing the format — via Open the Parquet file — row groups, pages, encodings
• Map a too-big scan to its layout cause — statistics, row groups, encodings — via Format-driven performance incidents — small scans and wrong layouts
• Explain how pruning fails when statistics are absent — via Format-driven performance incidents — small scans and wrong layouts
• Use the lifecycle's cost undercurrent to size the blast radius — via Format-driven performance incidents — small scans and wrong layouts

These resources map to stage: Foundations (2). Follow the four-phase roadmap to place this topic inside a progression instead of learning it in isolation.

Every entry, its shape and its trust state — sorted by the registry's composite score. This table is the honest version of a marketing comparison: no sponsored placements, no unverifiable claims.

How scores are computed: source quality score.

Highest composite score first:

1. Open the Parquet file — row groups, pages, encodings score 34.15 — beginner
2. Format-driven performance incidents — small scans and wrong layouts score 34.15 — intermediate

Scores rank provenance, completeness and trust — read how verification works before adopting anything.

Start here if you're new: Open the Parquet file — row groups, pages, encodings.

• Open the Parquet file — row groups, pages, encodings — A Parquet file is not a black box — it is row groups of column chunks made of pages, with statistics that readers use for predicate pushdown. Learn the anatomy from the two Parquet… details
• Format-driven performance incidents — small scans and wrong layouts — When a scan reads the whole lake for one column, the cause is usually the file layout, not the engine — missing statistics, row groups sized without intent, encodings chosen by def… details

Adjacent topics: tutorial (2 shared).

Study path: the roadmap places this topic in a progression · the scoring model explains the numbers · the trust rule catalog shows every security check these entries passed through.