caiconghui edited a comment on pull request #5712: URL: https://github.com/apache/incubator-doris/pull/5712#issuecomment-827551942
> Isn't it a bit unfriendly to not allow drop table, because the user may just want to drop the table due to some abnormality of the table. > After the table is dropped, it is reasonable to say that the task of schema change should directly fail. Why will it continue to be executed? if user want to use table again, the table should keep normal when recovered, but if schema change job not set table to be normal again, table will never be normal agagin. In fact, in a stand-alone environment, the table cannot be discarded because the table lock is held during the schema change operation. Because we consider performance here, the table lock is released part of the time during the entire execution of the schema change. Here we only need to cancel the alter table operation in time to drop successfully schema change should not directly fail, because some operation should not be interrupted, set table to be normal, clear unneeded tablet and so on if user really not need table anymore, he can use drop table force stmt which will clear all table meta immediatly -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
