[core] Support Deletion Vectors for Chain Table#8574
Open
juntaozhang wants to merge 4 commits into
Open
Conversation
juntaozhang
marked this pull request as draft
July 12, 2026 14:30
juntaozhang
force-pushed
the
support-chain-dv
branch
from
July 23, 2026 01:35
813db75 to
8322302
Compare
juntaozhang
force-pushed
the
support-chain-dv
branch
from
July 23, 2026 15:23
71cf2d8 to
2596eb3
Compare
juntaozhang
marked this pull request as ready for review
July 23, 2026 15:27
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.
Purpose
#8573
Tests
ChainSplitTesttestChainSplitSerdeWithDeletionFiles: verifies thatChainSplitcan carry deletion files alongside data files and correctly serialize/deserialize them.SplitSerializerTesttestV1Compatibility: ensures splits written before this change (without deletion files inChainSplit) can still be deserialized.v1tov2and asserts thatChainSplitround-trips its deletion files, branch mappings, and bucket paths.ChainTableFileStoreTableTesttestChainTableWithDelete: batch chain read withDELETErecords, covering bothdeletion-vectors.enabled=trueandfalse.testChainTableWithUpdate: batch chain read withUPDATErecords and DV enabled.testChainTableCrossPartitionDeletionVectors: chain read with group partitions (chain-table.chain-partition-keys) and DV, verifying that deletion vectors are scoped per group.testChainTableWithPartialUpdateDelete: confirms thatPARTIAL_UPDATE+partial-update.remove-record-on-delete=truestill works for chain tables without DV.testChainTableRejectsPartialUpdateWithDeletionVectors: validates that enabling DV on aPARTIAL_UPDATEchain table is rejected.testChainTableRejectsAggregate/testChainTableRejectsFirstRow: validates thatAGGREGATEandFIRST_ROWmerge engines are rejected for chain tables.FlinkChainTableITCasetestChainTableWithDeletionVectors: end-to-end Flink batch SQL with DV enabled, including snapshot/delta deletes, updates, andcompact_chain_table.testStreamingReadWithDeletionVectors: Flink streaming read over a chain table with DV, covering the full-load phase (snapshot DV applied) and incremental phase (deltacross-partition delete/update changelog).
SparkChainTableITCasetestChainTableWithDeletionVectors: Spark batch SQL with group partitions and DV enabled, verifying cross-branch deletes andcompact_chain_table.