Author: junrao
Date: Thu May 29 15:01:24 2014
New Revision: 1598314

URL: http://svn.apache.org/r1598314
Log:
Fix typo in introduction; patched by Chengwei Yang

Modified:
    kafka/site/08/introduction.html
    kafka/site/081/introduction.html

Modified: kafka/site/08/introduction.html
URL: 
http://svn.apache.org/viewvc/kafka/site/08/introduction.html?rev=1598314&r1=1598313&r2=1598314&view=diff
==============================================================================
--- kafka/site/08/introduction.html (original)
+++ kafka/site/08/introduction.html Thu May 29 15:01:24 2014
@@ -29,7 +29,7 @@ Each partition is an ordered, immutable 
 <p>
 The Kafka cluster retains all published messages&mdash;whether or not they 
have been consumed&mdash;for a configurable period of time. For example if the 
log retention is set to two days, then for the two days after a message is 
published it is available for consumption, after which it will be discarded to 
free up space. Kafka's performance is effectively constant with respect to data 
size so retaining lots of data is not a problem.
 <p>
-In fact the only metadata retained on a per-consumer basis is the position of 
the consumer in in the log, called the "offset". This offset is controlled by 
the consumer: normally a consumer will advance its offset linearly as it reads 
messages, but in fact the position is controlled by the consumer and it can 
consume messages in any order it likes. For example a consumer can reset to an 
older offset to reprocess.
+In fact the only metadata retained on a per-consumer basis is the position of 
the consumer in the log, called the "offset". This offset is controlled by the 
consumer: normally a consumer will advance its offset linearly as it reads 
messages, but in fact the position is controlled by the consumer and it can 
consume messages in any order it likes. For example a consumer can reset to an 
older offset to reprocess.
 <p>
 This combination of features means that Kafka consumers are very 
cheap&mdash;they can come and go without much impact on the cluster or on other 
consumers. For example, you can use our command line tools to "tail" the 
contents of any topic without changing what is consumed by any existing 
consumers.
 <p>

Modified: kafka/site/081/introduction.html
URL: 
http://svn.apache.org/viewvc/kafka/site/081/introduction.html?rev=1598314&r1=1598313&r2=1598314&view=diff
==============================================================================
--- kafka/site/081/introduction.html (original)
+++ kafka/site/081/introduction.html Thu May 29 15:01:24 2014
@@ -29,7 +29,7 @@ Each partition is an ordered, immutable 
 <p>
 The Kafka cluster retains all published messages&mdash;whether or not they 
have been consumed&mdash;for a configurable period of time. For example if the 
log retention is set to two days, then for the two days after a message is 
published it is available for consumption, after which it will be discarded to 
free up space. Kafka's performance is effectively constant with respect to data 
size so retaining lots of data is not a problem.
 <p>
-In fact the only metadata retained on a per-consumer basis is the position of 
the consumer in in the log, called the "offset". This offset is controlled by 
the consumer: normally a consumer will advance its offset linearly as it reads 
messages, but in fact the position is controlled by the consumer and it can 
consume messages in any order it likes. For example a consumer can reset to an 
older offset to reprocess.
+In fact the only metadata retained on a per-consumer basis is the position of 
the consumer in the log, called the "offset". This offset is controlled by the 
consumer: normally a consumer will advance its offset linearly as it reads 
messages, but in fact the position is controlled by the consumer and it can 
consume messages in any order it likes. For example a consumer can reset to an 
older offset to reprocess.
 <p>
 This combination of features means that Kafka consumers are very 
cheap&mdash;they can come and go without much impact on the cluster or on other 
consumers. For example, you can use our command line tools to "tail" the 
contents of any topic without changing what is consumed by any existing 
consumers.
 <p>


Reply via email to