-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](schema-change) Make sc job state updated after the table state is changed #42670
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 |
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. |
…is changed (apache#42670) Similar to apache#39327 Note that schema change job state and table state should be atomic and persistent, but neither is ensured by current implementation. We should optimize this point in the future.
…is changed (apache#42670) Similar to apache#39327 Note that schema change job state and table state should be atomic and persistent, but neither is ensured by current implementation. We should optimize this point in the future.
…table state is changed (#42879) PR Body: ## Proposed changes Similar to #39327 Note that schema change job state and table state should be atomic and persistent, but neither is ensured by current implementation. We should optimize this point in the future. Cherry-picked from #42670 Co-authored-by: Siyang Tang <82279870+TangSiyang2001@users.noreply.github.com>
Proposed changes
Similar to #39327
Note that schema change job state and table state should be atomic and persistent, but neither is ensured by current implementation. We should optimize this point in the future.