-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Fix](partial update) abort partial update on shadow index's tablet when the including columns miss key columns on new schema #46347
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Fix](partial update) abort partial update on shadow index's tablet when the including columns miss key columns on new schema #46347
Conversation
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
cc8956b to
1a307ef
Compare
|
run buildall |
TPC-H: Total hot run time: 32994 ms |
TPC-DS: Total hot run time: 190908 ms |
ClickBench: Total hot run time: 31.34 s |
|
TeamCity be ut coverage result: |
| "txn_id={}. Missing key column {}.", | ||
| tablet_id, txn_id, key_col.name()); | ||
| LOG_WARNING(msg); | ||
| return Status::Aborted<false>(msg); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is INVALID_SCHEMA error better?
zhannngchen
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
dataroaring
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…hen the including columns miss key columns on new schema (apache#46347) During a schema change which changes key columns, partial update on shadow index's tablet may cause duplicate key problem. So we abort the partial update in this situation.
…hen the including columns miss key columns on new schema (apache#46347) During a schema change which changes key columns, partial update on shadow index's tablet may cause duplicate key problem. So we abort the partial update in this situation.
What problem does this PR solve?
Problem Summary:
During a schema change which changes key columns, partial update on shadow index's tablet may cause duplicate key problem. So we abort the partial update in this situation.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)