add assertion that checksums.txt is consistent#76625
Merged
Conversation
Contributor
Member
Author
|
Fast tests showed that checksums file contains excess records about dropped projections. |
420835f to
1bf010c
Compare
Contributor
|
Dear @CheSema, this PR hasn't been updated for a while. Will you continue working on it? If not, please close it. Otherwise, ignore this message. |
1bf010c to
29d4585
Compare
29d4585 to
5620f7c
Compare
Contributor
1 task
Member
Author
3e1e422 to
739286a
Compare
Member
Author
That diаа was useful |
This reverts commit f54f818.
This was referenced Jul 15, 2025
Member
Author
|
Follow up #83830 |
baibaichen
pushed a commit
to Kyligence/gluten
that referenced
this pull request
Jul 18, 2025
baibaichen
pushed a commit
to Kyligence/gluten
that referenced
this pull request
Jul 18, 2025
This reverts commit 070e9315c28b8c8f948d402b8c2b3b5155e42855. due to ClickHouse/ClickHouse#83930
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It was possible to build wrong checksums.txt file during a sophisticated mutation or alter command.
After that the server might not be able to load it after restart or unable to remove that part when needed.
Here I add a check which runs for each committed part. It ensures that checksums.txt file matched the actual files on the disk. Otherwise transaction is aborted and part is not added to active parts set.
Along that I fixed all cases which have been triggered by that new check in our CI.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Verify the part has consistent checksum.txt file right before committing it.
Documentation entry for user-facing changes