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/06/23 03:30:39 UTC

[GitHub] [dolphinscheduler] CFlyGoo commented on issue #10562: [Improvement][dolphinscheduler-task-api] Support for multi-level environment variables

CFlyGoo commented on issue #10562:
URL: https://github.com/apache/dolphinscheduler/issues/10562#issuecomment-1163885207

   Then this seems to be a bug. I tried it on our project. When there is a value in my `Environment manage`, the settings in `dolphinscheduler_env.sh` did not take effect.
   
   ![image](https://user-images.githubusercontent.com/40393883/175202901-d5e40cba-893c-485a-8147-57d1201a6454.png)
   
   I found the following code in `org.apache.dolphinscheduler.plugin.task.api.ShellCommandExecutor#createCommandFileIfNotExists`.
   
   ![image](https://user-images.githubusercontent.com/40393883/175201979-c4ead74d-fc58-4998-afab-076a7a906b70.png)
   
   It seems that `dolphinscheudler_env.sh` will only take effect if there is no value in `Environment manage`.
   


-- 
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