-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](index compaction) forbid mor table to do index compaction #31102
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
Conversation
|
Thank you for your contribution to Apache Doris. |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 50209 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 240824 ms |
ClickBench: Total hot run time: 31.54 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
|
run p0 |
3f382a4 to
f943918
Compare
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 49932 ms |
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 237136 ms |
ClickBench: Total hot run time: 30.71 s |
|
Load test result on machine: 'aliyun_ecs.c7a.8xlarge_32C64G' |
xiaokang
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
Proposed changes
The
rowid_conversioncorrectness check is designed for MOW table.Since we allow MOR table to create inverted index, we should add limitation for the check.
If it's MOR table, we do not allow it to do index compaction temporarily, before we implement the
rowid_conversioncorrectness check for MOR table.Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...