public class EventLoggerBolt extends Object implements IBolt
Modifier and Type | Field and Description |
---|---|
static String |
FIELD_COMPONENT_ID |
static String |
FIELD_MESSAGE_ID |
static String |
FIELD_TS |
static String |
FIELD_VALUES |
Constructor and Description |
---|
EventLoggerBolt() |
Modifier and Type | Method and Description |
---|---|
void |
cleanup()
Called when an IBolt is going to be shutdown.
|
void |
execute(Tuple input)
Process a single tuple of input.
|
void |
prepare(Map<String,Object> topoConf,
TopologyContext context,
OutputCollector collector)
Called when a task for this component is initialized within a worker on the cluster.
|
public static final String FIELD_TS
public static final String FIELD_VALUES
public static final String FIELD_COMPONENT_ID
public static final String FIELD_MESSAGE_ID
public void prepare(Map<String,Object> topoConf, TopologyContext context, OutputCollector collector)
IBolt
This includes the:
prepare
in interface IBolt
topoConf
- 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)
IBolt
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.
public void cleanup()
IBolt
Config.SUPERVISOR_WORKER_SHUTDOWN_SLEEP_SECS
setting controls how long orderly shutdown is allowed to take.
There is no guarantee that cleanup will be called if shutdown is not orderly, or if the shutdown exceeds the time limit.
The one context where cleanup is guaranteed to be called is when a topology is killed when running Storm in local mode.
Copyright © 2023 The Apache Software Foundation. All rights reserved.