BenjaminWenqiYu opened a new issue #6314:
URL: https://github.com/apache/dolphinscheduler/issues/6314


   ### 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
   
   when I delete the processDefinition, it's related task cannot be deleted; 
then when I create another task instance with the same name will throw an error.
   First, when i create a process definition named 'shell_test', it has one 
task named 'shell_test';
   
![image](https://user-images.githubusercontent.com/41983209/134478972-3f3db594-6da2-4d46-9d72-36299a94a2df.png)
   Second, I delete the 'shell_test' process definition; it return success.
   
![image](https://user-images.githubusercontent.com/41983209/134479114-0870a9de-dab1-4384-a45d-a54b83ebf6a0.png)
   Third, i create a process definition the same as the first step. It will 
throw an exception.
   
![image](https://user-images.githubusercontent.com/41983209/134479477-1e60cba1-8876-4957-94ca-469e48a5aa69.png)
   Fourth, I query the database, I found the 'shell_test' task instance has not 
been deleted.
   
![image](https://user-images.githubusercontent.com/41983209/134479604-8d107c51-115c-4a9c-8a74-b76016da2be9.png)
   
   
   
   ### What you expected to happen
   
   When I delete the process definition, it will also delete it's task instance.
   
   ### How to reproduce
   
   It can be reproduced in dev branch.
   
   ### Anything else
   
   _No response_
   
   ### 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]


Reply via email to