-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Enhancement](storage) add a new hidden column __DORIS_VERSION_COL__ for unique key table #16509
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
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.
clang-tidy made some suggestions
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.
clang-tidy made some suggestions
|
clang-tidy review says "All clean, LGTM! 👍" |
|
TeamCity pipeline, clickbench performance test result: |
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
8ab0c83 to
7eeeae8
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
|
clang-tidy review says "All clean, LGTM! 👍" |
57755ab to
fbdc23c
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
1 similar comment
|
clang-tidy review says "All clean, LGTM! 👍" |
fbdc23c to
d7236b8
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
…for unique key table
d7236b8 to
67d0169
Compare
|
clang-tidy review says "All clean, LGTM! 👍" |
liaoxin01
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 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
|
PR approved by at least one committer and no changes requested. |
|
run compile |
…for unique key table (apache#16509)
…for unique key table (apache#16509)
…placed by fake version when merging tmp rowset in sort SC (#49193) ### What problem does this PR solve? When converting historical rowsets in sort schema change, it may write many temp rowsets and merge them into one rowset later if memory is not enough. However, these rowsets have fake versions which are like `[2^29+x, 2^29+x]`, so the values of `__DORIS_VERSION_COL__` in these temp rowsets will be wrongly replaced by these fake version(see #16509) in `Merger::vmerge_rowsets` when merging them into a single rowset. This PR modify these fake versions to avoid it.
…placed by fake version when merging tmp rowset in sort SC (#49193) ### What problem does this PR solve? When converting historical rowsets in sort schema change, it may write many temp rowsets and merge them into one rowset later if memory is not enough. However, these rowsets have fake versions which are like `[2^29+x, 2^29+x]`, so the values of `__DORIS_VERSION_COL__` in these temp rowsets will be wrongly replaced by these fake version(see #16509) in `Merger::vmerge_rowsets` when merging them into a single rowset. This PR modify these fake versions to avoid it.
…placed by fake version when merging tmp rowset in sort SC (apache#49193) ### What problem does this PR solve? When converting historical rowsets in sort schema change, it may write many temp rowsets and merge them into one rowset later if memory is not enough. However, these rowsets have fake versions which are like `[2^29+x, 2^29+x]`, so the values of `__DORIS_VERSION_COL__` in these temp rowsets will be wrongly replaced by these fake version(see apache#16509) in `Merger::vmerge_rowsets` when merging them into a single rowset. This PR modify these fake versions to avoid it.
Proposed changes
Issue Number: close #xxx
Problem summary
Only added to unique key table.
We've meet some data inconsistent issues, with this version column, it's much easier to locate issue.
For example:
Checklist(Required)
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...