HIVE-24991: Enable fetching deleted rows in vectorized mode #2264
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.
What changes were proposed in this pull request?
VectorizedOrcAcidRowBatchReader.java
:ROW__IS__DELETED
values for each row in the current batch.notDeletedBitSet
ROW__IS__DELETED
virtual columns is projected. If yes update the RowIsDeletedColumnVector field values bynotDeletedBitSet
and assign it to the result value batch.SortMergedDeleteEventRegistry
:When fetching deleted rows set the current writeId in the current batch of deleted rows. The new value is coming from the delete delta record.
ColumnizedDeleteEventRegistry
:SortMergedDeleteEventRegistry
. However to avoid unnecessary memory consumption current write ids of delete delta records are not stored when fetching deleted rows is off. To achieve this behavior write id loading/storing and marking deleted rows are extracted to classes:OriginalWriteIdLoader
/OriginalWriteIds
andBothWriteIdLoader
/BothWriteIds
Why are the changes needed?
Using vectorization boost the performance of fetching both deleted and not deleted records. This functionality is used by incremental materialized view maintenance.
Does this PR introduce any user-facing change?
No.
How was this patch tested?