-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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](merge-on-write) fix duplicate key in schema change #25705
Conversation
e35d004
to
5b7a20e
Compare
run buildall |
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
5b7a20e
to
d535e5d
Compare
run buildall |
fca5b0e
to
6823ca3
Compare
run buildall |
(From new machine)TeamCity pipeline, clickbench performance test result: |
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. |
6823ca3
to
e1a25a6
Compare
run buildall |
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
run buildall |
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. |
(From new machine)TeamCity pipeline, clickbench performance test result: |
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
It should be ensured that the obtained versions are continuous when calculate delete bitmap calculations in publish. The remaining NOTREADY tablet in the schema change failure should be dropped. When a rowset was deleted, the delete bitmap cannot be deleted until there are no read requests to use the rowset.
It should be ensured that the obtained versions are continuous when calculate delete bitmap calculations in publish. The remaining NOTREADY tablet in the schema change failure should be dropped. When a rowset was deleted, the delete bitmap cannot be deleted until there are no read requests to use the rowset.
It should be ensured that the obtained versions are continuous when calculate delete bitmap calculations in publish. The remaining NOTREADY tablet in the schema change failure should be dropped. When a rowset was deleted, the delete bitmap cannot be deleted until there are no read requests to use the rowset.
Proposed changes
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...