WilliamChen-luckbob opened a new issue #4696: URL: https://github.com/apache/incubator-dolphinscheduler/issues/4696
See issue[ #2561](https://github.com/apache/incubator-dolphinscheduler/issues/2561) So far, I can see how to input k-v pairs into a new process instance. Inspired by Azkaban and Airflow, I'm thinking about another situation like this : While starting a new process instance, sometimes the input parameters are not only k-v pairs or there are too many of them. It would be better if I can input only one JSON string instead of multiple k-v pair parameters when I'm starting a new process instance. Then dolphinscheduler transform and save it as a global map value. Other tasks may share this map using pattern ${aaa.bbb}. e.g. input is a complex JSON and each branch of the first floor may be the initialize data of each task { "a1" : { "a21":1, "a22":2 }, "b1":{ "b21":{ "b31":"xxxxx", "b32":"yyyyy" }, "b22":"cccccc" } } task1: uses init data ${a1} (which means the map includes a21 and a22 is required) task2: uses init data ${b1.b21.b31} (which means only xxxxx is required) ... So far, feature dev seems not support to pass a complex JSON while starting new process instance. I think It is conveniont for us if there are too many parameters, and also in the cases if tasks supports a dynamic parameter. On the other hand, inspired by azkaban, when 2 tasks has input-response-relationship, e.g. taskB requires the specified response from taskA, there should be someway to get and set those parameters. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
