Override the code that maps users to groups for authorization.

Specify the maximum time lag of the tuple timestamp in milliseconds. It means that the tuple timestamps cannot be out of order by more than this amoun

Specify a stream id on which late tuples are going to be emitted. They are going to be accessible via the {@link org.apache.storm.topology.WindowedBol

Run c with a local mode cluster overriding the NimbusClient and DRPCClient calls. NOTE local mode override happens by default now unless netty is turn

The maximum number of window events to keep in memory. This is meaningful only if {@link #withPersistence()} is also set. As the number of events in m

Specify the name of the field in the tuple that holds the message id. This is used to track the windowing boundaries and re-evaluating the windowing o

Output field names. Number of fields depends upon the reader type

If set, the stateful windowed bolt would use the backend state for window persistence and only keep a sub-set of events in memory as specified by {@li

Sets a user defined callback for use with the KafkaProducer. @param producerCallback user defined callback @return this

Specify the timestamp extractor implementation. @param timestampExtractor the {@link TimestampExtractor} implementation

The name of the field in the tuple that contains the timestamp when the event occurred as a long value. This is used of event-time based processing. I

Get worker outbound tasks. @return seq of task ids that receive messages from this worker

Would scheduling exec on ws fit? With a heap <= maxHeap total memory added <= memoryAvailable and cpu added <= cpuAvailable. @param ws

Would scheduling exec in ws fit with the current resource constraints. @param ws the slot to possibly put exec in @param exec the executor to possi

wrapJsonInCallback. @param callback callbackParameterName (must already be validated) @param response response @return wrapJsonInCallback