diff --git a/docs/api.html b/docs/api.html index 87ba559cae6..861eec3d20c 100644 --- a/docs/api.html +++ b/docs/api.html @@ -39,7 +39,7 @@ here.

2.2 Consumer API

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) diff --git a/docs/design.html b/docs/design.html index 5d3090cc85c..e0284685e91 100644 --- a/docs/design.html +++ b/docs/design.html @@ -27,9 +27,9 @@ It also meant the system would have to handle low-latency delivery to handle mor

We wanted to support partitioned, distributed, real-time processing of these feeds to create new, derived feeds. This motivated our partitioning and consumer model.

-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.

-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.

4.2 Persistence

Don't fear the filesystem!