public interface Stage
a computation step. It accepts input from its upstream stages (if any)
and passes its output to its downstream stages (if any). Jet
batch stages that represent
finite data sets (batches) and
stream stages that
represent infinite data streams. Some operations only make sense on a
batch stage and vice versa.
To build a pipeline, start with
get the initial stage and then use its methods to attach further
downstream stages. Terminate the pipeline by calling
stage.writeTo(sink), which will attach a
|Modifier and Type
|Method and Description
Pipeline this stage belongs to.
Returns the name of this stage.
Sets the preferred local parallelism (number of processors per Jet cluster member) this stage will configure its DAG vertices with.
Overrides the default name of the stage with the name you choose and returns the stage.
While most stages are backed by 1 vertex, there are exceptions. If a stage uses two vertices, each of them will have the given local parallelism, so in total there will be twice as many processors per member.
The default value is and it signals to Jet to figure out a default value. Jet will determine the vertex's local parallelism during job initialization from the global default and the processor meta-supplier's preferred value.
name - the stage name
Copyright © 2022 Hazelcast, Inc.. All rights reserved.