root
/
kafka
mirror of https://github.com/apache/kafka.git
1
0
Fork 0
Code Issues Actions 2 Packages Projects Releases Wiki Activity

KAFKA-2957: Fix typos in Kafka documentation 

Author: Vahid Hashemian <vahidhashemian@us.ibm.com>

Reviewers: Gwen Shapira

Closes #641 from vahidhashemian/KAFKA-2957

(cherry picked from commit 1f98b0315c)
Signed-off-by: Gwen Shapira <cshapi@gmail.com>
This commit is contained in:
Vahid Hashemian 2015-12-08 12:55:57 -08:00 committed by Gwen Shapira
parent 5bc90d4542
commit e1c4aefc36
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api.html
View File

@ -39,7 +39,7 @@ here</a>.
<h3><a id="consumerapi" href="#consumerapi">2.2 Consumer API</a></h3>
As of the 0.9.0 release we have added a new Java consumer to replace our existing high-level ZooKeeper-based consumer
and low-level consumer APIs. This client is considered beta quality. To ensure a smooth upgrade paths
and low-level consumer APIs. This client is considered beta quality. To ensure a smooth upgrade path
for users, we still maintain the old 0.8 consumer clients that continue to work on an 0.9 Kafka cluster.
In the following sections we introduce both the old 0.8 consumer APIs (both high-level ConsumerConnector and low-level SimpleConsumer)

4
docs/design.html
View File

@ -27,9 +27,9 @@ It also meant the system would have to handle low-latency delivery to handle mor
<p>
We wanted to support partitioned, distributed, real-time processing of these feeds to create new, derived feeds. This motivated our partitioning and consumer model.
<p>
Finally in cases where the stream is fed into other data systems for serving we knew the system would have to be able to guarantee fault-tolerance in the presence of machine failures.
Finally in cases where the stream is fed into other data systems for serving, we knew the system would have to be able to guarantee fault-tolerance in the presence of machine failures.
<p>
Supporting these uses led use to a design with a number of unique elements, more akin to a database log then a traditional messaging system. We will outline some elements of the design in the following sections.
Supporting these uses led us to a design with a number of unique elements, more akin to a database log than a traditional messaging system. We will outline some elements of the design in the following sections.
<h3><a id="persistence" href="#persistence">4.2 Persistence</a></h3>
<h4><a id="design_filesystem" href="#design_filesystem">Don't fear the filesystem!</a></h4>