You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2022/05/07 08:53:55 UTC
[GitHub] [dolphinscheduler] ruancheng77 commented on issue #9745: [Bug] [task-api] ${setValue(key=value)} alyways not success
ruancheng77 commented on issue #9745:
URL: https://github.com/apache/dolphinscheduler/issues/9745#issuecomment-1120168953
I think you seem to have misunderstood the root cause of the problem.
The problem I tested is that multithreading causes the shell script to use setValue syntax to set the variable value to pass out. Due to the influence of multithreading, the thread parsing setValue syntax may not parse in time, resulting in the lack of varpool.

--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org