MaouSanta opened a new issue, #18328: URL: https://github.com/apache/dolphinscheduler/issues/18328
### 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 I encountered a missing database column issue when upgrading Apache DolphinScheduler from version 3.2.2 to 3.3.1. After investigation, I found that the `3.2.2_schema/mysql/dolphinscheduler_ddl.sql` in the `3.2.2-release` branch is missing the following SQL statement: ```sql ALTER TABLE t_ds_project_parameter ADD `param_data_type` varchar(50) DEFAULT 'VARCHAR' COMMENT 'project parameter data type'; ``` However, this statement does exist under the `3.3.1-release` branch. Because my original deployment was already on version 3.2.2, the upgrade process to 3.3.1 did not re-execute the `3.2.2` incremental schema migration, which resulted in the `param_data_type` column being missing after the upgrade. ### What you expected to happen The schema migration files in the `3.2.2-release` branch and later release branches should remain consistent, or the upgrade process should ensure this column is added during later upgrades as well. ### How to reproduce * Source version: 3.2.2 * Target version: 3.3.1 * Database: MySQL ### Anything else Would it be better to add an idempotent migration in 3.3.0_schema to ensure this column exists? ### Version 3.3.1 ### 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]
