菜单
Run export_part tests in the s3 test suite. Use when the user wants to run export part tests, test ALTER TABLE EXPORT PART functionality, or test exporting MergeTree parts to S3.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Monitor MasterCI failures on a release branch (e.g. antalya-26.1) by cross-referencing the last N CI run reports. Use when the user asks to "check failing tests on branch X", "monitor a release branch", "see which tests are flaky on antalya-XX.X before release", or wants to know which failures are consistent vs flaky vs isolated across recent MasterCI runs.
Perform a static, distributed-systems-focused audit of a PR or feature. Use when reviewing changes to replication, cluster coordination, RPC/network paths, consensus- or Keeper-style dependencies, multi-node protocols, distributed state, retries/timeouts, or any logic whose correctness depends on behavior across nodes under partial failure.
Perform a usability audit of a feature, PR, or test suite from the user/operator's point of view and produce a clean list of issues they may face in normal flow, failure modes, cancellation, retries, concurrent admin actions, diagnostics, and at scale. Use when the user asks for a usability audit, user-journey trace, operator experience review, or wants a report of issues an operator may hit when using a feature. Also use proactively after completing a feature or PR audit to append an operational readiness section.
Write well-formatted GitHub issues for the Altinity ClickHouse repository following team conventions. Covers bug reports for regressions, upstream bugs, and flaky test tracking.
Analyze all CI failures in a Pull Request and categorize them as regressions, pre-existing flaky tests, infrastructure issues, or cascade failures.
Use the internal CI database to determine whether an Altinity regression test failure is flaky, a likely regression, or a new/unknown failure.
| name | export-part |
| description | Run export_part tests in the s3 test suite. Use when the user wants to run export part tests, test ALTER TABLE EXPORT PART functionality, or test exporting MergeTree parts to S3. |
Run tests for the ALTER TABLE ... EXPORT PART feature, which exports MergeTree parts from local tables to S3 storage.
All commands must be run from the s3 directory:
cd clickhouse-regression/s3
./regression.py --storage minio --clickhouse <URL> --only "<test-path>"
--clickhouse <URL> - URL to ClickHouse package (user must provide)--storage minio - Storage backend to use--only "<test-path>" - Test path pattern (must end with * to run all subtests)-l test.log - Save test logs to a file/s3/minio/export tests/export part/<feature>/*
The * wildcard is required to run all scenarios under a feature.
| Feature | Description |
|---|---|
sanity | Basic functionality (settings, empty tables, wide/compact parts) |
error handling | Invalid parts, disabled settings, corruption, pending mutations |
datatypes | Partition key types (Int, UInt, Date, DateTime, String, etc.) |
columns | ALIAS, MATERIALIZED, EPHEMERAL, DEFAULT, JSON, nested columns |
clusters nodes | Multi-node exports to same S3 destination |
shards | Distributed/sharded tables with Distributed engine |
engines volumes | Different table engines and volume configurations |
network | Packet delay, loss, corruption, MinIO/ClickHouse interruptions |
system monitoring | Events, part log, duplicate policies, metrics, bandwidth |
concurrent alter | ALTER operations before/during/after exports |
concurrent other | INSERT, SELECT, OPTIMIZE, KILL, DELETE during exports |
pending mutations and patch parts | Allowing exports with pending mutations |
rbac | ALTER INSERT privilege requirements |
table functions | Table function exports (explicit/inherited schema) |
Run all column tests:
./regression.py --storage minio --clickhouse https://example.com/clickhouse.deb --only "/s3/minio/export tests/export part/columns/*"
Run all sanity tests with logging:
./regression.py --storage minio --clickhouse https://example.com/clickhouse.deb --only "/s3/minio/export tests/export part/sanity/*" -l test.log
Run all export part tests:
./regression.py --storage minio --clickhouse https://example.com/clickhouse.deb --only "/s3/minio/export tests/export part/*"
Run a specific scenario (e.g., alias_columns under columns):
./regression.py --storage minio --clickhouse https://example.com/clickhouse.deb --only "/s3/minio/export tests/export part/columns/alias columns"