njnu-seafish opened a new issue, #18043:
URL: https://github.com/apache/dolphinscheduler/issues/18043

   ### 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
   
   The handle method in the ZeppelinTask class is missing the setVarPool call, 
causing parameter propagation to fail.
   
   > @Override
       public void handle(TaskCallBack taskCallBack) throws TaskException {
           try {
               ......
               // add response to out var poll
               addDefaultOutput(resultContent);
               // Use noteId-paragraph-Id as app id
               final int exitStatusCode = mapStatusToExitCode(status);
               setAppIds(String.format("%s-%s", noteId, paragraphId));
               setExitStatusCode(exitStatusCode);
               log.info("zeppelin task finished with results: {}", 
resultContent);
           } catch (Exception e) {
               setExitStatusCode(TaskConstants.EXIT_CODE_FAILURE);
               log.error("zeppelin task submit failed with error", e);
               throw new TaskException("Execute ZeppelinTask exception");
           }
       }
   
   ### What you expected to happen
   
   The ZeppelinTask task type successfully passes parameters to downstream 
tasks.
   
   ### How to reproduce
   
   Apologies, but I haven't set up a ZeppelinTask execution environment. 
However, based on the parameter passing logic of other task types, I can 
confirm that this bug exists.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   dev
   
   ### 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