Eonchpy opened a new issue #7367: URL: https://github.com/apache/dolphinscheduler/issues/7367
### 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 successfully upgrade dolphinscheduler from 1.3.8 to 2.0.0, however when checking the result I found out that none process instance or task instance which submitted from the old version could be displayed, but actually they still exist in the database, the reason seems to be because in _queryProcessInstanceListPaging_ the old version used _t_ds_process_instance.process_definition_id_ joined on _t_ds_process_definition.id_ but the new version used _t_ds_process_instance.process_definition_id_ joined on _t_ds_process_definition.code_. Can we fix this by modifying the column 'process_definition_code' of table 't_ds_process_instance' from id to the new code or what should we do to fix this. **BTW Is this means that the process submitted during upgrading could not been recovery after successfully upgraded.**   . ### What you expected to happen After upgrade we could not find any task or process that submitted from old version which really scarring me. And we are wondering that jobs submitted from old version could be recovery or not. ### How to reproduce upgrade to 2.0.0 when there do have jobs been submitted from old version's ds. ### Anything else _No response_ ### Version 2.0.0 ### Are you willing to submit PR? - [ ] 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]
