-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[bug](regression) fix regression test test-table-version in cloud_p0 #33462
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. Since 2024-03-18, the Document has been moved to doris-website. |
|
run buildall |
1 similar comment
|
run buildall |
|
run buildall |
1 similar comment
|
run buildall |
1e5f766 to
b39c183
Compare
|
run buildall |
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. |
|
PR approved by anyone and no changes requested. |
| long versionTime = System.currentTimeMillis(); | ||
| olapTable.updateVisibleVersionAndTime(version, versionTime); | ||
|
|
||
| long version = olapTable.getVisibleVersion(); |
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 this thread-safe?
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.
Users must obtain write lock of OlapTable before calling the dropPartition method.
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.
I found that the commit transaction holds a commit lock for the table. May be I need to hold a commit lock here?
Proposed changes
Issue Number: close #xxx
Fix regression test test-table-version.
introduce by:#32989
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...