[
https://issues.apache.org/jira/browse/KAFKA-2790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gwen Shapira resolved KAFKA-2790.
---------------------------------
Resolution: Fixed
Issue resolved by pull request 491
[https://github.com/apache/kafka/pull/491]
> Kafka 0.9.0 doc improvement
> ---------------------------
>
> Key: KAFKA-2790
> URL: https://issues.apache.org/jira/browse/KAFKA-2790
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.9.0.0
> Reporter: Jun Rao
> Assignee: Gwen Shapira
> Priority: Blocker
> Fix For: 0.9.0.0
>
>
> Observed a few issues after uploading the 0.9.0 docs to the Apache site
> (http://kafka.apache.org/090/documentation.html).
> 1. There are a few places still mentioning 0.8.2.
> docs/api.html:We are in the process of rewritting the JVM clients for Kafka.
> As of 0.8.2 Kafka includes a newly rewritten Java producer. The next release
> will include an equivalent Java consumer. These new clients are meant to
> supplant the existing Scala clients, but for compatability they will co-exist
> for some time. These clients are available in a seperate jar with minimal
> dependencies, while the old Scala clients remain packaged with the server.
> docs/api.html:As of the 0.8.2 release we encourage all new development to use
> the new Java producer. This client is production tested and generally both
> faster and more fully featured than the previous Scala client. You can use
> this client by adding a dependency on the client jar using the following
> example maven co-ordinates (you can change the version numbers with new
> releases):
> docs/api.html: <version>0.8.2.0</version>
> docs/ops.html:The partition reassignment tool does not have the ability to
> automatically generate a reassignment plan for decommissioning brokers yet.
> As such, the admin has to come up with a reassignment plan to move the
> replica for all partitions hosted on the broker to be decommissioned, to the
> rest of the brokers. This can be relatively tedious as the reassignment needs
> to ensure that all the replicas are not moved from the decommissioned broker
> to only one other broker. To make this process effortless, we plan to add
> tooling support for decommissioning brokers in 0.8.2.
> docs/quickstart.html:<a
> href="https://www.apache.org/dyn/closer.cgi?path=/kafka/0.8.2.0/kafka_2.10-0.8.2.0.tgz"
> title="Kafka downloads">Download</a> the 0.8.2.0 release and un-tar it.
> docs/quickstart.html:> <b>tar -xzf kafka_2.10-0.8.2.0.tgz</b>
> docs/quickstart.html:> <b>cd kafka_2.10-0.8.2.0</b>
> 2. The generated config tables (broker, producer and consumer) don't have the
> proper table frames.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)