docs: missing documentation for system.statistics system table

Open Beginner friendly
#3,217 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Quiet
Tech stack
rust
Domain
documentation

Research direction

Read src/query/storages/system/src/statistics_table.rs, especially the registered columns and statistics fields, then compare the structure and conventions of the system.columns and system.tables pages. Create docs/en/sql-reference/00-sql-reference/31-system-tables/system-statistics.md describing the table and its available data; done means the missing system.statistics page matches the surrounding documentation.

Written by the indexing model from the issue text.

Description

automated issue documentation

Missing Documentation: system.statistics

The system.statistics system table is implemented in the Databend source code but has no corresponding documentation page.

Source Code
  • File: src/query/storages/system/src/statistics_table.rs
  • Registered name: statistics (line 103)
What it does

The system.statistics table provides column-level statistics for all tables across all catalogs and databases. It exposes fields including column_name, database_name, table_name, and associated statistics data. It iterates over all catalogs, databases, and tables (including virtual columns) to collect per-column statistics.

Suggested doc location

docs/en/sql-reference/00-sql-reference/31-system-tables/system-statistics.md

Notes
  • All other system tables in src/query/storages/system/src/ have corresponding docs pages; this one is missing.
  • Related documented tables: system.columns, system.tables
Dominant language
TypeScript
Stars
17
Forks
44
Avg merge
2d 7m
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databendlabs/databend-docs

All issues in databendlabs/databend-docs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.