Author: junrao
Date: Sun Feb 2 05:02:14 2014
New Revision: 1563565
URL: http://svn.apache.org/r1563565
Log:
remove kafka.producer.async.CallbackHandler from 0.8 doc
Modified:
kafka/site/08/implementation.html
Modified: kafka/site/08/implementation.html
URL:
http://svn.apache.org/viewvc/kafka/site/08/implementation.html?rev=1563565&r1=1563564&r2=1563565&view=diff
==============================================================================
--- kafka/site/08/implementation.html (original)
+++ kafka/site/08/implementation.html Sun Feb 2 05:02:14 2014
@@ -26,7 +26,7 @@ The goal is to expose all the producer f
The new producer -
<ul>
<li>can handle queueing/buffering of multiple producer requests and
asynchronous dispatch of the batched data -
-<p><code>kafka.producer.Producer</code> provides the ability to batch multiple
produce requests (<code>producer.type=async</code>), before serializing and
dispatching them to the appropriate kafka broker partition. The size of the
batch can be controlled by a few config parameters. As events enter a queue,
they are buffered in a queue, until either <code>queue.time</code> or
<code>batch.size</code> is reached. A background thread
(<code>kafka.producer.async.ProducerSendThread</code>) dequeues the batch of
data and lets the <code>kafka.producer.EventHandler</code> serialize and send
the data to the appropriate kafka broker partition. A custom event handler can
be plugged in through the <code>event.handler</code> config parameter. At
various stages of this producer queue pipeline, it is helpful to be able to
inject callbacks, either for plugging in custom logging/tracing code or custom
monitoring logic. This is possible by implementing the
<code>kafka.producer.async.CallbackHandler</c
ode> interface and setting <code>callback.handler</code> config parameter to
that class.
+<p><code>kafka.producer.Producer</code> provides the ability to batch multiple
produce requests (<code>producer.type=async</code>), before serializing and
dispatching them to the appropriate kafka broker partition. The size of the
batch can be controlled by a few config parameters. As events enter a queue,
they are buffered in a queue, until either <code>queue.time</code> or
<code>batch.size</code> is reached. A background thread
(<code>kafka.producer.async.ProducerSendThread</code>) dequeues the batch of
data and lets the <code>kafka.producer.DefaultEventHandler</code> serialize and
send the data to the appropriate kafka broker partition.
</p>
</li>
<li>handles the serialization of data through a user-specified
<code>Encoder</code> -
