Signal that no more messages will be sent.
Signal that no more messages will be sent. Many implementations need this to do proper cleanup. This operation may happen asynchronously.
future that resolves when closing is complete
Request propagation of messages.
Request propagation of messages. The returned bitset contains the indexes of messages known to be sent successfully. Note that for some implementations, it is possible for a message to be sent and for the ack to be lost (e.g. if the send is occurring over a network).
a bitset containing indexes of messages that were sent successfully
Request propagation of messages.
Request propagation of messages. The return value indicates the number of messages known to be sent successfully. Note that for some implementations, it is possible for a message to be sent and for the ack to be lost (e.g. if the send is occurring over a network).
a batch of messages
the number of messages propagated
(Since version 0.7.0) use sendBatch
Beam composed of a stack of smaller beams. The smaller beams are split across two axes: timestamp (time shard of the data) and partition (shard of the data within one time interval). The stack of beams for a particular timestamp are created in a coordinated fashion, such that all ClusteredBeams for the same identifier will have semantically identical stacks. This interaction is mediated through zookeeper. Beam information persists across ClusteredBeam restarts.
In the case of Druid, each merged beam corresponds to one segment partition number, and each inner beam corresponds to either one index task or a set of redundant index tasks.