ClickHouse Code Review
Required context
Before reviewing, read:
AGENTS.mddocs/ai-review.md
If the review touches client-v2 or jdbc-v2, also read:
docs/features.md
Review workflow
- Identify the changed module and any compatibility-sensitive surfaces.
- Check correctness, regressions, API and behavior stability, JDBC or R2DBC semantics, and missing focused tests before style suggestions.
- Use common Java and driver behavior as a comparison aid, but preserve existing project behavior unless the change is intentionally user-visible.
- Report findings first, ordered by severity, then open questions or assumptions, then a brief summary.
Final response requirements
State:
- what changed
- whether compatibility risk exists
- what tests were run, or why they were not run
- whether docs should change
If no issues are found, say so explicitly and mention residual risk or testing gaps.