oxidecomputer / oxidecomputer/omicron
Consider enabling ClickHouse's `system.part_log` table
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
ClickHouse has a bunch of "system" tables, which expose various pieces of its own state and behavior. For example, we currently enable the query_log, which tracks all SQL queries with details about their resource usage. We should consider enabling the system.part_log table. This keeps historical information about how ClickHouse manages and merges data parts, such as compacting data after an insert or applying a mutation (e.g., dropping old data because of a TTL). The system.merges table is always there, but this only contains active merges.
Contributor guide
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.
Research direction
Start by finding the ClickHouse configuration that currently enables query_log, then review the server configuration documentation for system.part_log. Done means part_log is enabled alongside the existing query log and historical data-part operations, including merges and mutations, are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse
- Domain
- databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100