[Fix-16934][api] When creating workflows containing switch nodes in different orders, the copied workflows may lose associations.#16939
Merged
SbloodyS merged 3 commits intoapache:devfrom Jan 17, 2025
Conversation
…ifferent orders, the copied workflows may lose associations
Contributor
Author
|
@SbloodyS @caishunfeng PTAL |
SbloodyS
reviewed
Jan 6, 2025
...rc/main/java/org/apache/dolphinscheduler/api/service/impl/WorkflowDefinitionServiceImpl.java
Show resolved
Hide resolved
Contributor
Author
ruanwenjun
approved these changes
Jan 16, 2025
Member
ruanwenjun
left a comment
There was a problem hiding this comment.
LGTM.
The main diff is initialized the task code firstly.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Purpose of the pull request
Fix #16934
Brief change log
Verify this pull request
This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(or)
Pull Request Notice
Pull Request Notice
If your pull request contains incompatible change, you should also add it to
docs/docs/en/guide/upgrade/incompatible.md