Package org.apache.storm.trident.spout
Class RichSpoutBatchExecutor
java.lang.Object
org.apache.storm.trident.spout.RichSpoutBatchExecutor
- All Implemented Interfaces:
- Serializable,- ITridentDataSource,- ITridentSpout<Object>
- See Also:
- 
Nested Class SummaryNested classes/interfaces inherited from interface org.apache.storm.trident.spout.ITridentSpoutITridentSpout.BatchCoordinator<X>, ITridentSpout.Emitter<X>
- 
Field SummaryFields
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptiongetCoordinator(String txStateId, Map<String, Object> conf, TopologyContext context) The coordinator for a TransactionalSpout runs in a single thread and indicates when batches of tuples should be emitted.getEmitter(String txStateId, Map<String, Object> conf, TopologyContext context) The emitter for a TransactionalSpout runs as many tasks across the cluster.
- 
Field Details- 
MAX_BATCH_SIZE_CONF- See Also:
 
 
- 
- 
Constructor Details- 
RichSpoutBatchExecutor
 
- 
- 
Method Details- 
getComponentConfiguration- Specified by:
- getComponentConfigurationin interface- ITridentSpout<Object>
 
- 
getOutputFields- Specified by:
- getOutputFieldsin interface- ITridentSpout<Object>
 
- 
getCoordinatorpublic ITridentSpout.BatchCoordinator<Object> getCoordinator(String txStateId, Map<String, Object> conf, TopologyContext context) Description copied from interface:ITridentSpoutThe coordinator for a TransactionalSpout runs in a single thread and indicates when batches of tuples should be emitted. The Coordinator that you provide in a TransactionalSpout provides metadata for each transaction so that the transactions can be replayed in case of failure.Two instances are requested, one on the master batch coordinator where isReady() is called, and an instance in the coordinator bolt which is used for all other operations. The two instances do not necessarily share a worker JVM. - Specified by:
- getCoordinatorin interface- ITridentSpout<Object>
- Parameters:
- txStateId- stream id
- conf- Storm config map
- context- topology context
- Returns:
- spout coordinator instance
 
- 
getEmitterpublic ITridentSpout.Emitter<Object> getEmitter(String txStateId, Map<String, Object> conf, TopologyContext context) Description copied from interface:ITridentSpoutThe emitter for a TransactionalSpout runs as many tasks across the cluster. Emitters are responsible for emitting batches of tuples for a transaction and must ensure that the same batch of tuples is always emitted for the same transaction id.All emitter tasks get the same transaction metadata. The topology context parameter contains the instance task id that can be used to distribute the work across the tasks. - Specified by:
- getEmitterin interface- ITridentSpout<Object>
- Parameters:
- txStateId- stream id
- conf- Storm config map
- context- topology context
- Returns:
- spout emitter
 
 
-