Repository navigation
Spark: Backport forEachInRange vectorized delete checks to 3.5, 4.0 and 4.1 - #18207
Merged
Merged
Conversation
…nd 4.1 Backport of apache#18027. Both files are byte-identical to the Spark 4.2 versions.
JeonDaehong
changed the title
Contributor
Author
pvary
approved these changes
Sep 23, 2026
Contributor
|
Merged to main. |
Contributor
Author
Thank you! @pvary :D |
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.
Backport of #18027 to Spark 3.5, 4.0, and 4.1, as noted in that PR.
Both changed files are byte-identical to the Spark 4.2 versions merged in #18027:
ColumnarBatchUtil.buildRowIdMappingandbuildIsDeletedtraverse the position delete index once over the batch range instead of probing it once per row when the scan has no equality deletes.TestColumnarBatchUtiladds the range-traversal test cases from Core, Spark 4.2: Add PositionDeleteIndex.forEachInRange and use it in vectorized delete checks #18027.The core API (
PositionDeleteIndex.forEachInRange) is already on main, so this PR touches only the three Spark modules.Locally,
TestColumnarBatchUtilpasses on Spark 4.1 (17/17). The performance measurements are documented in #18027 and #18026 and were not re-run on the older Spark versions.