Skip to content

Conversation

@arthurpassos
Copy link
Collaborator

@arthurpassos arthurpassos commented Jan 22, 2026

Changelog category (leave one):

  • Improvement

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

Add query id to system.part_log, system_exports and system.replicated_partition_exports

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
Copy link
Collaborator Author

I don't think automated tests are required for such a change

@arthurpassos arthurpassos added antalya port-antalya PRs to be ported to all new Antalya releases antalya-25.8 labels Jan 22, 2026
@github-actions
Copy link

github-actions bot commented Jan 22, 2026

Workflow [PR], commit [fe41dbd]

{
auto context_copy = Context::createCopy(context);
context_copy->makeQueryContextForExportPart();
context_copy->setCurrentQueryId(manifest.transaction_id);
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You might be wondering why I was setting to transaction_id. Guess what: I don't remember :).

Honestly, I think it is simply because the query id was not being saved in the manifest and it wasn't available, so transaction_id sounded like a good replacement.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1a06f236ec

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

Comment on lines 156 to 159
ExportReplicatedMergeTreePartitionManifest manifest;
manifest.transaction_id = json->getValue<String>("transaction_id");
manifest.query_id = json->getValue<String>("query_id");
manifest.partition_id = json->getValue<String>("partition_id");

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Handle missing query_id in persisted manifests

This now requires query_id to be present in every persisted manifest JSON. Manifests created by older versions (or any already-queued exports before this change) won’t have that key, so json->getValue<String>("query_id") throws and the export cannot be resumed/inspected after upgrade. That can strand in-flight replicated exports until the manifest is manually fixed. Consider defaulting query_id to transaction_id or an empty string when the key is missing to keep backward compatibility.

Useful? React with 👍 / 👎.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As always, I have to explain: this feature is still very experimental and not used at all. Completely fine to make breaking changes

mkmkme
mkmkme previously approved these changes Jan 22, 2026
Copy link
Collaborator

@mkmkme mkmkme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

ianton-ru
ianton-ru previously approved these changes Jan 22, 2026
Copy link

@ianton-ru ianton-ru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@DimensionWieldr
Copy link
Collaborator

DimensionWieldr commented Jan 26, 2026

Export part test suite covers system.part_log and system.exports expected table columns. All tests pass.

Link to relevant test: https://github.com/Altinity/clickhouse-regression/blob/main/s3/tests/export_part/system_monitoring.py#L381

@Selfeer
Copy link
Collaborator

Selfeer commented Jan 26, 2026

Wrote an automated tests that checks every field is present and populated after export partition in system.replicated_partition_exports - all tests pass.

link to tests: https://github.com/Altinity/clickhouse-regression/blob/0a049a9dcdf96b5396277be15e8c8f120f4950fb/s3/tests/export_partition/system_monitoring.py#L338

Passing

✔ [ OK ] '/s3/minio/export tests/export partition/system monitoring/all required fields present' (10s 109ms)
✔ [ OK ] '/s3/minio/export tests/export partition/system monitoring' (10s 110ms)
✔ [ OK ] '/s3/minio/export tests/export partition' (54s 582ms)
✔ [ OK ] '/s3/minio/export tests' (54s 596ms)
✔ [ OK ] '/s3/minio' (1m 43s)
✔ [ OK ] '/s3' (1m 43s)

@Selfeer Selfeer added verified Verified by QA and removed verified Verified by QA labels Jan 26, 2026
@zvonand
Copy link
Collaborator

zvonand commented Jan 27, 2026

03321_clickhouse_local_initialization_not_too_slow_even_under_sanitizers is failing twice in the latest run

@CarlosFelipeOR CarlosFelipeOR dismissed stale reviews from mkmkme and ianton-ru via fe41dbd January 28, 2026 13:27
@Selfeer
Copy link
Collaborator

Selfeer commented Jan 28, 2026

Summary of Failed Tests and Root Causes

Test name Status Reason for failure
03321_clickhouse_local_initialization_not_too_slow_even_under_sanitizers Failed Startup-performance canary for clickhouse-local. Within the ~10-second window, clickhouse-local -q 1 started, executed, and exited 9 times, while the test expects at least 10. This indicates slower-than-expected process initialization on this CI run, not a functional or correctness issue. The test logic itself has not changed recently (last edited ~11 months ago in upstream master), suggesting an environment/runtime performance issue rather than a test change.
test_s3_cache_locality/test.py::test_cache_locality[0] Failed Marked as BROKEN after the last CI/CD run so it will be included in the broken list on the next run.
export_part related tests Failed The commit hash was outdated, so an old version of export_part was used. Some of the failing tests no longer exist, as they have been renamed or updated.

@Selfeer Selfeer added the verified Verified by QA label Jan 28, 2026
@Selfeer
Copy link
Collaborator

Selfeer commented Jan 28, 2026

The CI/CD run is expected to be red, we will monitor the final run in the branch. @arthurpassos please merge this PR.

@arthurpassos
Copy link
Collaborator Author

The CI/CD run is expected to be red, we will monitor the final run in the branch. @arthurpassos please merge this PR.

I don't have the powers to do it. Perhaps @zvonand

@zvonand
Copy link
Collaborator

zvonand commented Jan 28, 2026

94 jobs are in progress yet

@MyroTk MyroTk merged commit f3a7dce into antalya-25.8 Jan 29, 2026
524 of 728 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants