public abstract class BaseStatefulBoltExecutor extends Object implements IRichBolt
Base class that abstracts the common logic for executing bolts in a stateful topology.
Modifier and Type | Class and Description |
---|---|
protected static class |
BaseStatefulBoltExecutor.AnchoringOutputCollector |
Modifier and Type | Field and Description |
---|---|
protected OutputCollector |
collector |
Constructor and Description |
---|
BaseStatefulBoltExecutor() |
Modifier and Type | Method and Description |
---|---|
protected void |
declareCheckpointStream(OutputFieldsDeclarer declarer) |
void |
execute(Tuple input)
Process a single tuple of input.
|
protected abstract void |
handleCheckpoint(Tuple checkpointTuple,
CheckPointState.Action action,
long txid)
Sub-classes can implement the logic for handling checkpoint tuple.
|
protected abstract void |
handleTuple(Tuple input)
Sub-classes can implement the logic for handling the tuple.
|
protected void |
init(TopologyContext context,
OutputCollector collector) |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
declareOutputFields, getComponentConfiguration
protected OutputCollector collector
protected void init(TopologyContext context, OutputCollector collector)
public void execute(Tuple input)
IBolt
Process a single tuple of input. The Tuple object contains metadata on it about which component/stream/task it came from. The values of the Tuple can be accessed using Tuple#getValue. The IBolt does not have to process the Tuple immediately. It is perfectly fine to hang onto a tuple and process it later (for instance, to do an aggregation or join).
Tuples should be emitted using the OutputCollector provided through the prepare method. It is required that all input tuples are acked or failed at some point using the OutputCollector. Otherwise, Storm will be unable to determine when tuples coming off the spouts have been completed.
For the common case of acking an input tuple at the end of the execute method, see IBasicBolt which automates this.
protected void declareCheckpointStream(OutputFieldsDeclarer declarer)
protected abstract void handleTuple(Tuple input)
Sub-classes can implement the logic for handling the tuple.
input
- the input tupleprotected abstract void handleCheckpoint(Tuple checkpointTuple, CheckPointState.Action action, long txid)
Sub-classes can implement the logic for handling checkpoint tuple.
checkpointTuple
- the checkpoint tupleaction
- the action (prepare, commit, rollback or initstate)txid
- the transaction id.Copyright © 2022 The Apache Software Foundation. All rights reserved.