Export partition all

[arthurpassos]

Changelog category (leave one):

• New feature

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

Introduce the export partition all command, which schedules exports for all partitions in a given table. Introduce a setting to control scheduling failure behavior

Documentation entry for user-facing changes

...

CI/CD Options

Exclude tests:

• Fast test
• Integration Tests
• Stateless tests
• Stateful tests
• Performance tests
• All with ASAN
• All with TSAN
• All with MSAN
• All with UBSAN
• All with Coverage
• All with Aarch64
• All Regression
• Disable CI Cache

Regression jobs to run:

• Fast suites (mostly <1h)
• Aggregate Functions (2h)
• Alter (1.5h)
• Benchmark (30m)
• ClickHouse Keeper (1h)
• Iceberg (2h)
• LDAP (1h)
• Parquet (1.5h)
• RBAC (1.5h)
• SSL Server (1h)
• S3 (2h)
• S3 Export (2h)
• Swarms (30m)
• Tiered Storage (2h)

[github-actions]

Workflow [PR], commit [5ddfe97]

[chatgpt-codex-connector]

💡 Codex Review

ClickHouse/tests/queries/0_stateless/03609_export_merge_tree_partition_all.sh

Line 32 in 0eb7a47

query "ALTER TABLE $rmt_table EXPORT PARTITION ALL TO TABLE $s3_table SETTINGS allow_experimental_export_merge_tree_part = 1"

Poll instead of sleeping for partition exports

This test relies on a fixed 15-second delay after EXPORT PARTITION ALL, but the ALTER only schedules asynchronous per-partition export tasks. On slower CI or object-storage backends the exports can legitimately take longer, so the following read from the S3 table can race and report missing rows even though the feature works. Poll system.replicated_partition_exports for the expected partition ids to reach COMPLETED before querying the destination, as the integration tests do.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[mkmkme]

Looks good! I would definitely add this feature to the documentation though

[mkmkme]

Nit: Seems irrelevant to the feature