fix(core): fix incorrect truncation of WAL table partition leading to read errors #3451
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.
Fix WAL table writing bug which can lead to incorrect partition data truncation. This then manifests in the reading error similar to
The issue was that Table Writer did not advance column files truncate positions under certain circumstances before switching to the next partition while applying WAL. This results in the incorrect trimming of the partition and if the trimming difference is bigger than File page size it leads to read errors like the one listed above.