You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be useful if the Framework pipelines would accept and pass around (to reach worker pipelines) a string parameter that could contain Json. It would allow one or more "dynamic parameters".
For exemple, if I would like to create a daily Tumbling Window Trigger and pass the particular day to load to the framework so that it reaches my workers pipelines, I could simply build a Json string containing the information.
Another example would be the use of a Storage Event Trigger or Custom Event Trigger to start a batch execution. It would provide a way to pass dynamic information (ex. @triggerBody().folderPath and @triggerBody().fileName).
I hope my suggestion is clear and that others see value in it.
The text was updated successfully, but these errors were encountered:
I think it would be useful if the Framework pipelines would accept and pass around (to reach worker pipelines) a string parameter that could contain Json. It would allow one or more "dynamic parameters".
For exemple, if I would like to create a daily Tumbling Window Trigger and pass the particular day to load to the framework so that it reaches my workers pipelines, I could simply build a Json string containing the information.
Another example would be the use of a Storage Event Trigger or Custom Event Trigger to start a batch execution. It would provide a way to pass dynamic information (ex. @triggerBody().folderPath and @triggerBody().fileName).
I hope my suggestion is clear and that others see value in it.
The text was updated successfully, but these errors were encountered: