kafka git commit: MINOR: Add upgrade notes for KIP-62

[jg...@apache.org]

Repository: kafka
Updated Branches:
  refs/heads/trunk 672dfaa24 -> 1a396c9cf


MINOR: Add upgrade notes for KIP-62

Author: Jason Gustafson <ja...@confluent.io>

Reviewers: Guozhang Wang <wa...@gmail.com>

Closes #1956 from hachikuji/add-kip-62-upgrade-notes


Project: http://git-wip-us.apache.org/repos/asf/kafka/repo
Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/1a396c9c
Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/1a396c9c
Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/1a396c9c

Branch: refs/heads/trunk
Commit: 1a396c9cf22441a7afa8ec9c4a94a48f881cdd90
Parents: 672dfaa
Author: Jason Gustafson <ja...@confluent.io>
Authored: Mon Oct 3 21:17:11 2016 -0700
Committer: Jason Gustafson <ja...@confluent.io>
Committed: Mon Oct 3 21:17:11 2016 -0700

----------------------------------------------------------------------
 docs/upgrade.html | 1 +
 1 file changed, 1 insertion(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kafka/blob/1a396c9c/docs/upgrade.html
----------------------------------------------------------------------
diff --git a/docs/upgrade.html b/docs/upgrade.html
index 4f9d4f2..4f23a95 100644
--- a/docs/upgrade.html
+++ b/docs/upgrade.html
@@ -64,6 +64,7 @@ Note: Because new protocols are introduced, it is important to upgrade your Kafk
     <li> Kafka clusters can now be uniquely identified by a cluster id. It will be automatically generated when a broker is upgraded to 0.10.1.0. The cluster id is available via the kafka.server:type=KafkaServer,name=ClusterId metric and it is part of the Metadata response. Serializers, client interceptors and metric reporters can receive the cluster id by implementing the ClusterResourceListener interface. </li>
     <li> The BrokerState "RunningAsController" (value 4) has been removed. Due to a bug, a broker would only be in this state briefly before transitioning out of it and hence the impact of the removal should be minimal. The recommended way to detect if a given broker is the controller is via the kafka.controller:type=KafkaController,name=ActiveControllerCount metric. </li>
     <li> The new Java Consumer now allows users to search offsets by timestamp on partitions. </li>
+    <li> The new Java Consumer now supports heartbeating from a background thread. There is a new configuration <code>max.poll.interval.ms</code> which controls the maximum time between poll invocations before the consumer will proactively leave the group (5 minutes by default). The default value of <code>session.timeout.ms</code> has been adjusted down to 10 seconds, and the default value of <code>max.poll.records</code> has been changed to 500.</li>
     <li> When using an Authorizer and a user doesn't have <b>Describe</b> authorization on a topic, the broker will no
          longer return TOPIC_AUTHORIZATION_FAILED errors to requests since this leaks topic names. Instead, the UNKNOWN_TOPIC_OR_PARTITION
          error code will be returned. This may cause unexpected timeouts or delays when using the producer and consumer since