kafka-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jun...@apache.org
Subject svn commit: r1478066 - in /kafka/site/08: api.html configuration.html includes/header.html quickstart.html
Date Wed, 01 May 2013 16:05:06 GMT
Author: junrao
Date: Wed May  1 16:05:06 2013
New Revision: 1478066

URL: http://svn.apache.org/r1478066
Log:
fix typos in 0.8 docs

Modified:
    kafka/site/08/api.html
    kafka/site/08/configuration.html
    kafka/site/08/includes/header.html
    kafka/site/08/quickstart.html

Modified: kafka/site/08/api.html
URL: http://svn.apache.org/viewvc/kafka/site/08/api.html?rev=1478066&r1=1478065&r2=1478066&view=diff
==============================================================================
--- kafka/site/08/api.html (original)
+++ kafka/site/08/api.html Wed May  1 16:05:06 2013
@@ -4,7 +4,7 @@
 <pre>
 /**
  *  V: type of the message
- *  K: type of the optional key assciated with the message
+ *  K: type of the optional key associated with the message
  */
 class kafka.javaapi.producer.Producer&lt;K,V&gt;
 {
@@ -139,7 +139,7 @@ class kafka.javaapi.consumer.SimpleConsu
   public void close();
 }
 </pre>
-For most applications, the high level consumer Api is good enough. Some applications want
features not exposed to the high level consumer yet (e.g., set initial offset when restarting
the consumer). They can instead use our low level SimpleConsumer Api. The logic will be a
bit more complicated and you can follow the examples in
+For most applications, the high level consumer Api is good enough. Some applications want
features not exposed to the high level consumer yet (e.g., set initial offset when restarting
the consumer). They can instead use our low level SimpleConsumer Api. The logic will be a
bit more complicated and you can follow the example in
 <a href="https://cwiki.apache.org/confluence/display/KAFKA/0.8.0+SimpleConsumer+Example"
title="Kafka 0.8 SimpleConsumer example">here</a>.
 
 <h3>Kafka Hadoop Consumer</h3>
@@ -153,4 +153,3 @@ Usage information on the hadoop consumer
 </p>
 
 <!--#include virtual="includes/footer.html" -->
-

Modified: kafka/site/08/configuration.html
URL: http://svn.apache.org/viewvc/kafka/site/08/configuration.html?rev=1478066&r1=1478065&r2=1478066&view=diff
==============================================================================
--- kafka/site/08/configuration.html (original)
+++ kafka/site/08/configuration.html Wed May  1 16:05:06 2013
@@ -403,7 +403,7 @@
       <td>request.required.acks</td>
       <td colspan="1">0</td>
       <td>
-        <p>This value controls when the producer receives an acknowledgement from the
broker. Typical values are (1) 0, which means that the producer never waits for an acknowledgement
from the broker (the same behavior as 0.7); (2) 1, which means that the producer gets an acknowledgement
after the leader replica has received the data; (3) -1, which means that the producer gets
an acknowledgement after all in-sync replicas have received the data. The first option provides
the lowest latency (no network delay), but the worst durabilty (some data loss when the leader
replica fails). The second option provides lower latency (one network round trip) and better
durability (few data loss when the leader replica fails). The last option provides low latency
(two network round trips) and the best durability (no data loss as long as the number of failed
brokers is less the replication factor of the topic).</p>
+        <p>This value controls when the producer receives an acknowledgement from the
broker. Typical values are (1) 0, which means that the producer never waits for an acknowledgement
from the broker (the same behavior as 0.7); (2) 1, which means that the producer gets an acknowledgement
after the leader replica has received the data; (3) -1, which means that the producer gets
an acknowledgement after all in-sync replicas have received the data. The first option provides
the lowest latency (no network delay), but the worst durability (some data loss when the leader
replica fails). The second option provides lower latency (one network round trip) and better
durability (few data loss when the leader replica fails). The last option provides low latency
(two network round trips) and the best durability (no data loss as long as the number of failed
brokers is less the replication factor of the topic).</p>
      </td>
     </tr>
     <tr>
@@ -507,3 +507,5 @@
 	
 
 </div></body></html>
+
+<!--#include virtual="includes/footer.html" -->

Modified: kafka/site/08/includes/header.html
URL: http://svn.apache.org/viewvc/kafka/site/08/includes/header.html?rev=1478066&r1=1478065&r2=1478066&view=diff
==============================================================================
--- kafka/site/08/includes/header.html (original)
+++ kafka/site/08/includes/header.html Wed May  1 16:05:06 2013
@@ -29,7 +29,7 @@
                                                 <ul>
 							<li><a href="quickstart.html">quickstart</a></li>
 							<li><a href="design.html">design</a></li>
-                                        		<li><a href="api.html">api docs</a></li>
+                                        		<li><a href="api.html">api examples</a></li>
                                         		<li><a href="configuration.html">configuration</a></li>
 							<li><a href="tools.html">tools</a></li>
 						</ul>

Modified: kafka/site/08/quickstart.html
URL: http://svn.apache.org/viewvc/kafka/site/08/quickstart.html?rev=1478066&r1=1478065&r2=1478066&view=diff
==============================================================================
--- kafka/site/08/quickstart.html (original)
+++ kafka/site/08/quickstart.html Wed May  1 16:05:06 2013
@@ -31,7 +31,6 @@ First start the zookeeper server. You ca
 Now start the Kafka server:
 <pre>
 <b>&gt; bin/kafka-server-start.sh config/server.properties</b>
-jkreps-mn-2:kafka-trunk jkreps$ bin/kafka-server-start.sh config/server.properties 
 [2013-04-22 15:01:47,028] INFO Verifying properties (kafka.utils.VerifiableProperties)
 [2013-04-22 15:01:47,051] INFO Property socket.send.buffer.bytes is overridden to 1048576
(kafka.utils.VerifiableProperties)
 ...
@@ -75,4 +74,3 @@ If you want to set up replication on mor
 </pre>
 
 <!--#include virtual="includes/footer.html" -->
-



Mime
View raw message