Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like your way of solving this. I do have also the logic for solving this like -
However, I didn't change the AddRouteOperator logic. This thing will also work, I think my approach will be more overhead. Want your thought to it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I compared two solutions if they build the same JobGraphs or not.
The JobGraphs look like the same except:
my solution:
your solution:
So it really has some overhead - not in additional vertexes, but in additional logic in the route transformation operator.
Nevertheless I prefer to not include control events to the stream before the routing. The main advantage - it won't be ambiguous.