T → N × TFan-Out Processing with the Split Operator
Broadcasts each value to multiple downstream consumers.
When to use
Use Split to make intentional fan-out explicit and allow several consumers.
Behavior
- Every consumer receives the same value.
- No function or output type configuration is needed.
General properties
Identity, ownership and operator-specific mode.
typeTransformationTypeOperator kind. It controls available properties, valid sources and generated interfaces.
RequiredAllowed:Input, SubStream, Map, Filter, Join, MultiJoin, Process, FlatMap, FlatMapIterable, KeyBy, Merge, Split, Case, Sink, CycleLink, Error, Delay, WhennamestringHuman-readable stream name shown in the designer and used to derive default generated symbols.
RequiredserviceServiceService that owns the stream. Connected streams must belong to the same service.
RequiredConnections properties
Upstream graph references accepted by this operator.
sourceStreamSingle upstream stream. The designer only offers structurally and type-compatible candidates.
RequiredExecution properties
Pipeline placement and runtime policy.
pipelinestringNamed business-flow grouping inside the owning service; retained in generated configuration and runtime grouping metadata. It does not create connections.
Position properties
Designer-only canvas coordinates.
xPosnumberHorizontal designer coordinate. It has no runtime effect; missing positions can be supplied by layout.
yPosnumberVertical designer coordinate. It has no runtime effect; missing positions can be supplied by layout.
Configuration example
type: Split
source: normalizedOrder