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
When compiling a sub-graph within a larger graph, under specific conditions, the START and END nodes of the sub-graph are included in the larger graph. When the START or END nodes have more than 1 edge outgoing or incoming, respectively, the nodes are included. They are omitted otherwise. Is this intended behaviour? I assume so, as it adds clarity to the fully compiled graph. However I assume there is some kind of performance impact with adding redundant nodes. Would an optional flag to disable the redunadant organizational nodes when compiling be a good idea?
This is inspired by this issue: /issues/1676
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When compiling a sub-graph within a larger graph, under specific conditions, the START and END nodes of the sub-graph are included in the larger graph. When the START or END nodes have more than 1 edge outgoing or incoming, respectively, the nodes are included. They are omitted otherwise. Is this intended behaviour? I assume so, as it adds clarity to the fully compiled graph. However I assume there is some kind of performance impact with adding redundant nodes. Would an optional flag to disable the redunadant organizational nodes when compiling be a good idea?
This is inspired by this issue:
/issues/1676
Beta Was this translation helpful? Give feedback.
All reactions