yang100455 opened a new issue #6127:
URL: https://github.com/apache/dolphinscheduler/issues/6127


   
   **Describe the feature**
   In the current version, global parameters can only be assigned when the 
[process_definition] is defined. After the [process_definition] goes online, 
global parameters cannot be dynamically assigned for each [process_instance] 
first started, which is not flexible enough to use.
   
   I think we should add a feature,When a new process instance is started,  the 
highest global parameters can be defined, 
   the old global parameters within the [process_definition] can be overridden.
   
   
   **Is your feature request related to a problem? Please describe.**
   What business scenarios can this feature solve?
   answer:
   In addition to ETL tasks, there are some offline tasks where we can abstract 
logic to dolphins,But the run parameters are indeterminate and need to be 
determined by the caller.
   For example, [user path analysis],You need to start the Spark analysis task 
based on the analysis time range and event range,At this point we can 
dynamically pass in these parameters, and then use dolphin's complete 
scheduling and alarm mechanism to complete the task and fault tolerance.
   
   **Describe the solution you'd like**
   I simply implemented this function myself. Functionally I expect so, but the 
implementation could be better
   
![image](https://user-images.githubusercontent.com/43943331/132440963-c3f6b102-ec8b-4d31-b8f1-afa4d2473e20.png)
   
   What I have simply implemented is a newly started [process instance] with 
[my global parameters json] passed in as the highest priority, but without 
changing the original [process_definition] or affecting other process 
instances, and with fault tolerance.
   
   
   **Describe alternatives you've considered**
   A similar implementation, Azkaban, overrides the placeholders by starting 
the task with an incoming parameter
   
   **Additional context**
   
   


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