[fix](binlog) Commit table stream offsets for empty inserts - #67126
Open
luwei16 wants to merge 1 commit into
Open
[fix](binlog) Commit table stream offsets for empty inserts#67126luwei16 wants to merge 1 commit into
luwei16 wants to merge 1 commit into
Conversation
### What problem does this PR solve? Issue Number: close apache#66273 Related PR: None Problem Summary: When the optimizer reduces an INSERT INTO SELECT from a Table Stream to an empty relation, the previous empty-insert shortcut bypasses the transaction lifecycle. The target receives zero rows, but the stream offset is not committed, so the same stream state can be read repeatedly. Keep empty Table Stream reads in the transaction lifecycle, skip coordinator data execution, and commit the offset atomically. Ordinary empty inserts continue to use the existing fast-return path. ### Release note Table Stream offsets now advance when INSERT INTO SELECT succeeds with zero rows. ### Check List (For Author) - Test: Unit Test - InsertIntoTableCommandTableStreamTest and OlapInsertExecutorTest (21 tests) - ./build.sh --fe -j 192 - Behavior changed: Yes (successful zero-row Table Stream inserts now commit offsets; ordinary inserts are unchanged) - Does this need documentation: No
luwei16
requested review from
924060929,
englefly,
morrySnow and
starocean999
as code owners
August 25, 2026 10:02
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
Contributor
FE UT Coverage ReportIncrement line coverage |
Contributor
TPC-H: Total hot run time: 16814 ms |
Contributor
TPC-DS: Total hot run time: 81622 ms |
Contributor
ClickBench: Total hot run time: 14.79 s |
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.
What problem does this PR solve?
Issue Number: close #66273
Related PR: None
Problem Summary: When the optimizer reduces an INSERT INTO SELECT from a Table Stream to an empty relation, the previous empty-insert shortcut bypasses the transaction lifecycle. The target receives zero rows, but the stream offset is not committed, so the same stream state can be read repeatedly. Keep empty Table Stream reads in the transaction lifecycle, skip coordinator data execution, and commit the offset atomically. Ordinary empty inserts continue to use the existing fast-return path.
Release note
Table Stream offsets now advance when INSERT INTO SELECT succeeds with zero rows.
Check List (For Author)