Core: Partition prune delete manifests in ManifestFilterManager - #18154
Open
grantatspothero wants to merge 3 commits into
Open
grantatspothero wants to merge 3 commits into
grantatspothero wants to merge 3 commits into
Conversation
grantatspothero
force-pushed
the
gn/pruneDeleteManifestScanForDanglingDVs
branch
2 times, most recently
from
September 17, 2026 15:21
e80b3f8 to
ffb5a5a
Compare
grantatspothero
force-pushed
the
gn/pruneDeleteManifestScanForDanglingDVs
branch
2 times, most recently
from
September 17, 2026 15:44
b76776c to
634fca2
Compare
canContainDroppedFiles only checked minSequenceNumber inside the removedDataFilePaths branch, so a commit that calls dropDeleteFilesOlderThan without also removing data files (e.g. a plain append) never admitted delete manifests for that check, and obsolete delete files were silently never dropped in that case.
…ataFilesBenchmark The benchmark builds an unpartitioned table on the local filesystem, so it cannot show the cost of reading or writing manifests. A local open takes well under a millisecond while an object store charges tens of milliseconds per round trip, and manifest work against remote storage is dominated by those round trips rather than by decoding.
Removing data files makes every DV that references them dangling, so ManifestFilterManager scans delete manifests to find them. Previously canContainDroppedFiles admitted every delete manifest unconditionally, so a commit that replaces data files opened every delete manifest. Now uses partition pruning to determine which delete manifests to open. This mirrors partition pruning done with data manifests.
grantatspothero
force-pushed
the
gn/pruneDeleteManifestScanForDanglingDVs
branch
from
September 18, 2026 17:34
634fca2 to
6dca9e2
Compare
Contributor
Author
|
cc: @nastra since you built the referencing PR. |
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.
This PR: #13222 added support for tracking removed data files during MergingSnapshotProducer so that orphan DV could be removed.
The purpose of this PR is to increase performance of delete manifest filtering/rewriting through partition pruning delete manifests. See below commit breakdown:
3 commits in this PR:
canContainDroppedFilesimplementation for dangling DV detection.RewriteDataFilesBenchmarkbenchmark. I tried to make the benchmark more realistic (injecting object-storage like latency, using a partitioned table, etc).JMH results:
commit (2)
commit (3):
Most of the benchmark shows no change as expected, the notable improvements are for the "large partitioned table with realistic object storage latency" cases:
(2)
(3):