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
hkube version: 1.1.171v Is your feature request related to a problem? Please describe.
I run subpipeline, then I have more nodes (or subpipelines) that depend on different subpipeline nodes result. Dependency includes also non-final nodes in the subpipeline.
I have an Algorithm which calls the subpipeline, then collect its node results and return this.
There's no way (in this version) to get the non-final nodes results.
Also, I need an access by name to the results (e.g. @SubpipeNode.Node1 would give the result of Node1 in the subpipeline), so other nodes/subpipelines can depend on them.
Describe the solution you'd like
Best solution is having a flag for that in hkube_python_wrapper: subpipe_response = hkube_api.start_stored_subpipeline(name, flowInput, blocking=True, include_non_final=True)
Describe alternatives you've considered
Currently I'm forced to create another final node for each non-final node I need in the rest of the flow - just an eval-alg based echo function that returns the result as-is. That's very clumsy and make the graph even more unreadable for no reason!
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
implemented in #685
the user can specify, for each node in the pipeline, it they want to include the result of this node in the final result.
sink nodes are always included
hkube version: 1.1.171v
Is your feature request related to a problem? Please describe.
I run subpipeline, then I have more nodes (or subpipelines) that depend on different subpipeline nodes result. Dependency includes also non-final nodes in the subpipeline.
I have an Algorithm which calls the subpipeline, then collect its node results and return this.
There's no way (in this version) to get the non-final nodes results.
Also, I need an access by name to the results (e.g.
@SubpipeNode.Node1
would give the result of Node1 in the subpipeline), so other nodes/subpipelines can depend on them.Describe the solution you'd like
Best solution is having a flag for that in hkube_python_wrapper:
subpipe_response = hkube_api.start_stored_subpipeline(name, flowInput, blocking=True, include_non_final=True)
Describe alternatives you've considered
Currently I'm forced to create another final node for each non-final node I need in the rest of the flow - just an eval-alg based echo function that returns the result as-is.
That's very clumsy and make the graph even more unreadable for no reason!
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: