Is your feature request related to a problem? Please describe.
In the current iteration of the new schema changer, we prevent DROP TABLE from pre-empting ongoing schema change jobs and return an error. It's not clear that this is good behavior.
This is something to think about, but, for now, is for the backlog. The good news is that in the new schema changer, all job cancelation should be fast.
Is your feature request related to a problem? Please describe. In the current iteration of the new schema changer, we prevent
DROP TABLE
from pre-empting ongoing schema change jobs and return an error. It's not clear that this is good behavior.Jira issue: CRDB-3048