Index: 082/configuration.html
===================================================================
--- 082/configuration.html	(revision 1706297)
+++ 082/configuration.html	(working copy)
@@ -867,6 +867,10 @@
 	<tr>
 	<td>acks</td><td>string</td><td>1</td><td>high</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. This controls the  durability of records that are sent. The following settings are common:  <ul> <li><code>acks=0</code> If set to zero then the producer will not wait for any acknowledgment from the server at all. The record will be immediately added to the socket buffer and considered sent. No guarantee can be made that the server has received the record in this case, and the <code>retries</code> configuration will not take effect (as the client won't generally know of any failures). The offset given back for each record will always be set to -1. <li><code>acks=1</code> This will mean the leader will write the record to its local log but will respond without awaiting full acknowledgement from all followers. In this case should the leader fail immediately after acknowledging the record but before the followers have replicated it then the record will be lost. <li><code>acks=all</code> This means the leader will wait for the full set of in-sync replicas to acknowledge the record. This guarantees that the record will not be lost as long as at least one in-sync replica remains alive. This is the strongest available guarantee. <li>Other settings such as <code>acks=2</code> are also possible, and will require the given number of acknowledgements but this is generally less useful.</td></tr>
 	<tr>
+        <td>key.serializer</td><td>string</td><td></td><td>high</td><td>A string that indicates the serializer class used for the key of a message. For example, "org.apache.kafka.common.serialization.StringSerializer" and "org.apache.kafka.common.serialization.ByteArraySerializer". User can also write their own serializer by implementing the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</td></tr>
+	<tr>
+        <td>value.serializer</td><td>string</td><td></td><td>high</td><td>A string that indicates the serializer class used for the value of a message. For example, "org.apache.kafka.common.serialization.StringSerializer" and "org.apache.kafka.common.serialization.ByteArraySerializer". User can also write their own serializer by implementing the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</td></tr>
+	<tr>
 	<td>buffer.memory</td><td>long</td><td>33554432</td><td>high</td><td>The total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered to the server the producer will either block or throw an exception based on the preference specified by <code>block.on.buffer.full</code>. <p>This setting should correspond roughly to the total memory the producer will use, but is not a hard bound since not all memory the producer uses is used for buffering. Some additional memory will be used for compression (if compression is enabled) as well as for maintaining in-flight requests.</td></tr>
 	<tr>
 	<td>compression.type</td><td>string</td><td>none</td><td>high</td><td>The compression type for all data generated by the producer. The default is none (i.e. no compression). Valid  values are <code>none</code>, <code>gzip</code>, or <code>snappy</code>. Compression is of full batches of data,  so the efficacy of batching will also impact the compression ratio (more batching means better compression).</td></tr>
Index: 083/configuration.html
===================================================================
--- 083/configuration.html	(revision 1706297)
+++ 083/configuration.html	(working copy)
@@ -867,6 +867,10 @@
 	<tr>
 	<td>acks</td><td>string</td><td>1</td><td>high</td><td>The number of acknowledgments the producer requires the leader to have received before considering a request complete. This controls the  durability of records that are sent. The following settings are common:  <ul> <li><code>acks=0</code> If set to zero then the producer will not wait for any acknowledgment from the server at all. The record will be immediately added to the socket buffer and considered sent. No guarantee can be made that the server has received the record in this case, and the <code>retries</code> configuration will not take effect (as the client won't generally know of any failures). The offset given back for each record will always be set to -1. <li><code>acks=1</code> This will mean the leader will write the record to its local log but will respond without awaiting full acknowledgement from all followers. In this case should the leader fail immediately after acknowledging the record but before the followers have replicated it then the record will be lost. <li><code>acks=all</code> This means the leader will wait for the full set of in-sync replicas to acknowledge the record. This guarantees that the record will not be lost as long as at least one in-sync replica remains alive. This is the strongest available guarantee. <li>Other settings such as <code>acks=2</code> are also possible, and will require the given number of acknowledgements but this is generally less useful.</td></tr>
 	<tr>
+        <td>key.serializer</td><td>string</td><td></td><td>high</td><td>A string that indicates the serializer class used for the key of a message. For example, "org.apache.kafka.common.serialization.StringSerializer" and "org.apache.kafka.common.serialization.ByteArraySerializer". User can also write their own serializer by implementing the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</td></tr>
+	<tr>
+        <td>value.serializer</td><td>string</td><td></td><td>high</td><td>A string that indicates the serializer class used for the value of a message. For example, "org.apache.kafka.common.serialization.StringSerializer" and "org.apache.kafka.common.serialization.ByteArraySerializer". User can also write their own serializer by implementing the <code>org.apache.kafka.common.serialization.Serializer</code> interface.</td></tr>
+	<tr>
 	<td>buffer.memory</td><td>long</td><td>33554432</td><td>high</td><td>The total bytes of memory the producer can use to buffer records waiting to be sent to the server. If records are sent faster than they can be delivered to the server the producer will either block or throw an exception based on the preference specified by <code>block.on.buffer.full</code>. <p>This setting should correspond roughly to the total memory the producer will use, but is not a hard bound since not all memory the producer uses is used for buffering. Some additional memory will be used for compression (if compression is enabled) as well as for maintaining in-flight requests.</td></tr>
 	<tr>
 	<td>compression.type</td><td>string</td><td>none</td><td>high</td><td>The compression type for all data generated by the producer. The default is none (i.e. no compression). Valid  values are <code>none</code>, <code>gzip</code>, or <code>snappy</code>. Compression is of full batches of data,  so the efficacy of batching will also impact the compression ratio (more batching means better compression).</td></tr>