docs: missing documentation for system.backtrace system table
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- sql
- Domain
- documentation
Research direction
Read src/query/storages/system/src/backtrace_table.rs to confirm the registered name and columns, then compare the structure of docs/en/sql-reference/00-sql-reference/31-system-tables/system-query-log.md. Create the suggested system-backtrace.md with a schema table and example SELECT query; done means the system.backtrace table is documented in the same format.
Written by the indexing model from the issue text.
Description
Missing Documentation: system.backtrace
The system.backtrace system table is implemented in Databend but has no documentation in databend-docs.
Source Code
/workspace/databend/src/query/storages/system/src/backtrace_table.rs
Registered as: system.backtrace (constant NAME = "system.backtrace")
What it does
Exposes the current async task backtraces for all running tasks across warehouse nodes. Each row contains:
node— the cluster node namequery_id— the associated query IDstack_trace— the backtrace/stack trace string for the task
Useful for diagnosing hung queries or debugging async runtime issues in a distributed Databend deployment.
Suggested Doc Location
/docs/en/sql-reference/00-sql-reference/31-system-tables/system-backtrace.md
Should follow the same format as other system table docs (e.g. system-query-log.md), including a schema table and example SELECT query.
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databendlabs/databend-docs
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
databendlabs/databend-docs#3504 ·
-
Link Checker Report Openautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
databendlabs/databend-docs#3503 ·
-
auto-fix-done documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
databendlabs/databend-docs#3359 ·
-
auto-fix-done documentation
Difficulty 2/5 1-2 days Newbie friendliness 72/100
databendlabs/databend-docs#3356 ·
-
auto-fix documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
databendlabs/databend-docs#3302 ·
All issues in databendlabs/databend-docs
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100