Eric-YBC opened a new issue, #17318:
URL: https://github.com/apache/dolphinscheduler/issues/17318

   ### 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
   
   We deployed the dolphinscheduler 3.3.0 alpha version by k8s, but i can not 
delete task or add dependent task to my workflow, is this a bug of 3.3.0 alpha 
version?
   
   
![Image](https://github.com/user-attachments/assets/54500955-ada2-407e-86c3-ca28c6fc03a5)
   
![Image](https://github.com/user-attachments/assets/cabbe038-75a6-4691-8fc1-15831af2b30b)
   
   ### What you expected to happen
   
   I checked the version 3.3.0 source code for github
   
[https://github.com/apache/dolphinscheduler/blob/457dafe3cc6cdf6b86e98f535908017573[…]es/sql/upgrade/3.3.0_schema/postgresql/dolphinscheduler_ddl.sql](https://github.com/apache/dolphinscheduler/blob/457dafe3cc6cdf6b86e98f53590801757338bb45/dolphinscheduler-dao/src/main/resources/sql/upgrade/3.3.0_schema/postgresql/dolphinscheduler_ddl.sql)
   and I found the DDL of the same table from different database(mysql/pg) is 
not the same and have some issues.
   In mysql DDL,  The column id from t_ds_workflow_task_lineage is 
AUTO_INCREMENT, but in PG the id from t_ds_workflow_task_lineage  is just the 
primary key not bigserial , i think it's maybe a bug and should be fixed
   
   ### How to reproduce
   
   N/A
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.3.0-alpha
   
   ### 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