A duplicate key property error occurs when defining two tasks with the same OUT parameter name in a process

[fanzhenyu95]

Search before asking

• [X] I had searched in the issues and found no similar issues.

What happened

I have defined a workflow that includes two tasks of the stored procedure type, each with an OUT parameter named "result". When executed, a duplicate key property error occurs.

I have reviewed the source code, and the error is caused by the following line of code:

I suspect that this error is related to the up and downstream parameter passing function. How can I resolve this issue?

What you expected to happen

How can this error be avoided? Or, how can we support the scenario where the upstream and downstream stored procedure type tasks in a workflow have OUT parameters with the same name?

How to reproduce

Define a workflow that includes more than two tasks of the stored procedure type, each containing an OUT parameter with the same name, and then execute this workflow.

Anything else

No response

Version

dev

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

[wangxj3]

If the parameter with the same name should be overridden, the parameter generated by the node with the latest downstream or end time shall prevail

[fanzhenyu95]

Thank you for your replies to my questions.

The Procedure Task did not call the dealOutParam method in AbstractParameters class. If I am using version 3.2.1 of DolphinScheduler, should I fix this issue by following this PR(#16420) in the dealOutParam4Procedure method of ProcedureParameters class?