@PublicEvolving public class FromSplittableIteratorFunction<T> extends RichParallelSourceFunction<T>
SourceFunction that reads elements from an SplittableIterator and emits them.SourceFunction.SourceContext<T>| Constructor and Description |
|---|
FromSplittableIteratorFunction(SplittableIterator<T> iterator) |
| Modifier and Type | Method and Description |
|---|---|
void |
cancel()
Cancels the source.
|
void |
open(Configuration parameters)
Initialization method for the function.
|
void |
run(SourceFunction.SourceContext<T> ctx)
Starts the source.
|
close, getIterationRuntimeContext, getRuntimeContext, setRuntimeContextpublic FromSplittableIteratorFunction(SplittableIterator<T> iterator)
public void open(Configuration parameters) throws Exception
RichFunctionThe configuration object passed to the function can be used for configuration and initialization. The configuration contains all parameters that were configured on the function in the program composition.
public class MyMapper extends FilterFunction<String> {
private String searchString;
public void open(Configuration parameters) {
this.searchString = parameters.getString("foo");
}
public boolean filter(String value) {
return value.equals(searchString);
}
}
By default, this method does nothing.
open in interface RichFunctionopen in class AbstractRichFunctionparameters - The configuration containing the parameters attached to the contract.Exception - Implementations may forward exceptions, which are caught by the runtime. When the
runtime catches an exception, it aborts the task and lets the fail-over logic
decide whether to retry the task execution.Configurationpublic void run(SourceFunction.SourceContext<T> ctx) throws Exception
SourceFunctionSourceFunction.SourceContext emit
elements.
Sources that implement CheckpointedFunction
must lock on the checkpoint lock (using a synchronized block) before updating internal
state and emitting elements, to make both an atomic operation:
public class ExampleCountSource implements SourceFunction<Long>, CheckpointedFunction {
private long count = 0L;
private volatile boolean isRunning = true;
private transient ListState<Long> checkpointedCount;
public void run(SourceContext<T> ctx) {
while (isRunning && count < 1000) {
// this synchronized block ensures that state checkpointing,
// internal state updates and emission of elements are an atomic operation
synchronized (ctx.getCheckpointLock()) {
ctx.collect(count);
count++;
}
}
}
public void cancel() {
isRunning = false;
}
public void initializeState(FunctionInitializationContext context) {
this.checkpointedCount = context
.getOperatorStateStore()
.getListState(new ListStateDescriptor<>("count", Long.class));
if (context.isRestored()) {
for (Long count : this.checkpointedCount.get()) {
this.count = count;
}
}
}
public void snapshotState(FunctionSnapshotContext context) {
this.checkpointedCount.clear();
this.checkpointedCount.add(count);
}
}
ctx - The context to emit elements to and for accessing locks.Exceptionpublic void cancel()
SourceFunctionSourceFunction.run(SourceContext) method. The implementation needs to ensure that the
source will break out of that loop after this method is called.
A typical pattern is to have an "volatile boolean isRunning" flag that is set to
false in this method. That flag is checked in the loop condition.
When a source is canceled, the executing thread will also be interrupted
(via Thread.interrupt()). The interruption happens strictly after this
method has been called, so any interruption handler can rely on the fact that
this method has completed. It is good practice to make any flags altered by
this method "volatile", in order to guarantee the visibility of the effects of
this method to any interruption handler.
Copyright © 2014–2020 The Apache Software Foundation. All rights reserved.