-
Notifications
You must be signed in to change notification settings - Fork 392
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
[#3326] feat(jdbc-doris): output the alter status of table into the log #3332
Conversation
// sql is `SHOW ALTER TABLE COLUMN WHERE TableName = 'test_table'` | ||
// database name must be specified in connection, so the SQL do not need to specify database | ||
// name | ||
String sql = String.format("SHOW ALTER TABLE COLUMN WHERE TableName = '%s' limit 1", tableName); |
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.
Can alter table operation be executed in serialization?
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.
NO, as metioned in https://doris.apache.org/docs/1.2/advanced/alter-table/schema-change/
Because the Schema Chanage job is an asynchronous operation, only one Schema chanage job can be performed on the same table at the same time. To check the operation status of the job, you can use the following command
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
… the log (apache#3332) ### What changes were proposed in this pull request? Output the alter status of table into the log ### Why are the changes needed? Fix: apache#3326 ### Does this PR introduce _any_ user-facing change? N/A ### How was this patch tested? Manual, check log
What changes were proposed in this pull request?
Output the alter status of table into the log
Why are the changes needed?
Fix: #3326
Does this PR introduce any user-facing change?
N/A
How was this patch tested?
Manual, check log