wendongdi opened a new issue, #11875: URL: https://github.com/apache/dolphinscheduler/issues/11875
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened exceptions is thrown while running UpgradeDolphinScheduler with profle 'upgrade': - Duplicate key exceptions are thrown when upgrading mysql-meta-data by executing ver. 2.0.3~ver. 2.0.4 dolphinscheduler_ddl.sql ,like this:  - An exception occurred while dropping an index that does not exist by executing ver. 3.1.0 dolphinscheduler_ddl.sql  - Duplicate column exceptions are thrown when upgrading mysql-meta-data by executing ver. 3.1.1 dolphinscheduler_ddl.sql ,such as :  ### What you expected to happen I think the upgrade process is important and shouldn't have any exceptions, and appended upgrade processes must take into account the case of duplicates of indexes or columns or tables ### How to reproduce I recommend defining mysql procedures to determine whether an index or column already exists, and if it exists, delete it and then create a new one; then exception dropping an index that does not exist occurs because of a sql logic error and easy to fix it;  ### Anything else I recommend that subsequent versions of the mysql sql script also need to avoid these exceptions ### Version dev ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
