export part - skip or throw on pending mutations and patch parts

[arthurpassos]

Changelog category (leave one):

• Improvement

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

Add export_merge_tree_part_throw_on_pending_mutations and export_merge_tree_part_throw_on_pending_patch_parts to control the behavior of pending mutations / patch parts on the export part feature. By default it will throw. It is important to note that when exporting an outdated it will never throw.

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)
• Tiered Storage (2h)

[arthurpassos]

One sec and I will adapt it for export partition

[github-actions]

Workflow [PR], commit [dd10dda]

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 28e124685d

ℹ️ 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".

[chatgpt-codex-connector]

Decouple mutation skipping from patch-part checks

Here need_alter_mutations is forced on whenever patch-part checks are enabled. Because IMutationsSnapshot::needIncludeMutationToSnapshot always includes metadata/alter mutations regardless of need_data_mutations, pending_mutations will still be non-empty and the export will throw even when export_merge_tree_part_throw_on_pending_mutations=false (e.g., a pending ALTER ADD COLUMN with default patch-part settings). That makes the new “skip pending mutations” setting ineffective unless users also disable patch-part checks, which contradicts the intended independent controls.

Useful? React with 👍 / 👎.