Add support for single operator nodes in YAML dataflow specification #50
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.
Single operator nodes are specified through an
operator
field, in contrast to theoperators
list of normal runtime nodes. Since there is only a single operator on such nodes, specifying an additional operator ID is not necessary. If no operator ID is given, thecoordinator
will assign the IDop
.Other nodes can also reference outputs of single-operator nodes by only specifying the node ID, the operator ID is optional here as well. The coordinator will automatically resolve these links.
This feature is useful for Python operators because all operators on the same node use a single global interpreter lock (GIL). By using a separate node for each Python operator, they run in different processes without GIL contention.