public class TestEventOrderCheckBolt extends BaseRichBolt
| Modifier and Type | Field and Description |
|---|---|
static org.slf4j.Logger |
LOG |
| Constructor and Description |
|---|
TestEventOrderCheckBolt() |
| Modifier and Type | Method and Description |
|---|---|
void |
cleanup()
Called when an IBolt is going to be shutdown.
|
void |
declareOutputFields(OutputFieldsDeclarer declarer)
Declare the output schema for all the streams of this topology.
|
void |
execute(Tuple input)
Process a single tuple of input.
|
Fields |
getOutputFields() |
void |
prepare(Map stormConf,
TopologyContext context,
OutputCollector collector)
Called when a task for this component is initialized within a worker on the cluster.
|
getComponentConfigurationclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitgetComponentConfigurationpublic void prepare(Map stormConf, TopologyContext context, OutputCollector collector)
IBoltCalled when a task for this component is initialized within a worker on the cluster. It provides the bolt with the environment in which the bolt executes.
This includes the:
stormConf - The Storm configuration for this bolt. This is the configuration provided to the topology merged in with cluster configuration on this machine.context - This object can be used to get information about this task’s place within the topology, including the task id and component id of this task, input and output information, etc.collector - The collector is used to emit tuples from this bolt. Tuples can be emitted at any time, including the prepare and cleanup methods. The collector is thread-safe and should be saved as an instance variable of this bolt object.public void execute(Tuple input)
IBoltProcess 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.
input - The input tuple to be processed.public void cleanup()
IBoltCalled when an IBolt is going to be shutdown. There is no guarentee that cleanup will be called, because the supervisor kill -9’s worker processes on the cluster.
The one context where cleanup is guaranteed to be called is when a topology is killed when running Storm in local mode.
cleanup in interface IBoltcleanup in class BaseRichBoltpublic Fields getOutputFields()
public void declareOutputFields(OutputFieldsDeclarer declarer)
IComponentDeclare the output schema for all the streams of this topology.
declarer - this is used to declare output stream ids, output fields, and whether or not each output stream is a direct streamCopyright © 2019 The Apache Software Foundation. All Rights Reserved.