mchcz opened a new issue #6973: URL: https://github.com/apache/dolphinscheduler/issues/6973
### 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 **BACKGROUND:** The current version is upgraded from 1.0.2 to 1.3.5, and now the test is upgraded from 1.3.5 to 2.0.0 **Q1:** Some older versions of the generated jason do not have **tenantId** fields Code: processDefinition.setTenantId (jsonObject.get ("tenantId"));asInt(); **Q2:** Some older versions of the generated json do not have **description** fields Code: taskDefinitionLog.setDescription ("description").asText()); **Q3:** Some older versions of the generated json do not have **workerGroup** field Code: taskDefinitionLog.setWorkerGroup ("workergroup").asText(); **Q4:** Dependencies in a workflow that do not exist in the source workflow (dependency disabled, deleted in the source workflow) are abnormal. Code: long taskCode , "ALL".equals (depTasks)? 0L : processCodeTaskNameCodeEntry.getValue().get(depTasks); **Q5:** When the json split is complete, look at the workflow dependency information, the code is shown on the page and the workflow cannot be selected, and the log is reported as duplicate key Error information: Duplicate key (through reference chain: org.apache.dolphinscheduler.dao.entity.TaskDefinitionLog."taskParamMap") ### What you expected to happen It can be upgraded to version 2.0.0 normally ### How to reproduce Described in "What happened" ### Anything else _No response_ ### Version 2.0.0-alpha ### 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]
