Repository: kafka Updated Branches: refs/heads/trunk 91135ea33 -> 7fd4fe448
MINOR: Fix javadoc typos in ConsumerRebalanceListener Author: Vahid Hashemian <[email protected]> Reviewers: Ismael Juma <[email protected]> Closes #1500 from vahidhashemian/typo07/fix_javadoc_typos_consumerrebalancelistener Project: http://git-wip-us.apache.org/repos/asf/kafka/repo Commit: http://git-wip-us.apache.org/repos/asf/kafka/commit/7fd4fe44 Tree: http://git-wip-us.apache.org/repos/asf/kafka/tree/7fd4fe44 Diff: http://git-wip-us.apache.org/repos/asf/kafka/diff/7fd4fe44 Branch: refs/heads/trunk Commit: 7fd4fe4487d328da0aab80ac658ba783ff1ebf9b Parents: 91135ea Author: Vahid Hashemian <[email protected]> Authored: Sun Jun 19 10:42:30 2016 +0200 Committer: Ismael Juma <[email protected]> Committed: Sun Jun 19 10:42:30 2016 +0200 ---------------------------------------------------------------------- .../consumer/ConsumerRebalanceListener.java | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/kafka/blob/7fd4fe44/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerRebalanceListener.java ---------------------------------------------------------------------- diff --git a/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerRebalanceListener.java b/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerRebalanceListener.java index 8af405c..938d22b 100644 --- a/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerRebalanceListener.java +++ b/clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerRebalanceListener.java @@ -3,9 +3,9 @@ * file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file * to You under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the * License. You may obtain a copy of the License at - * + * * http://www.apache.org/licenses/LICENSE-2.0 - * + * * Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on * an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the * specific language governing permissions and limitations under the License. @@ -20,23 +20,23 @@ import org.apache.kafka.common.TopicPartition; * A callback interface that the user can implement to trigger custom actions when the set of partitions assigned to the * consumer changes. * <p> - * This is applicable when the consumer is having Kafka auto-manage group membership. If the consumer's directly assign partitions, + * This is applicable when the consumer is having Kafka auto-manage group membership. If the consumer directly assigns partitions, * those partitions will never be reassigned and this callback is not applicable. * <p> - * When Kafka is managing the group membership, a partition re-assignment will be triggered any time the members of the group changes or the subscription + * When Kafka is managing the group membership, a partition re-assignment will be triggered any time the members of the group change or the subscription * of the members changes. This can occur when processes die, new process instances are added or old instances come back to life after failure. - * Rebalances can also be triggered by changes affecting the subscribed topics (e.g. when then number of partitions is + * Rebalances can also be triggered by changes affecting the subscribed topics (e.g. when the number of partitions is * administratively adjusted). * <p> * There are many uses for this functionality. One common use is saving offsets in a custom store. By saving offsets in - * the {@link #onPartitionsRevoked(Collection)}, call we can ensure that any time partition assignment changes + * the {@link #onPartitionsRevoked(Collection)} call we can ensure that any time partition assignment changes * the offset gets saved. * <p> * Another use is flushing out any kind of cache of intermediate results the consumer may be keeping. For example, * consider a case where the consumer is subscribed to a topic containing user page views, and the goal is to count the - * number of page views per users for each five minute window. Let's say the topic is partitioned by the user id so that - * all events for a particular user will go to a single consumer instance. The consumer can keep in memory a running - * tally of actions per user and only flush these out to a remote data store when its cache gets to big. However if a + * number of page views per user for each five minute window. Let's say the topic is partitioned by the user id so that + * all events for a particular user go to a single consumer instance. The consumer can keep in memory a running + * tally of actions per user and only flush these out to a remote data store when its cache gets too big. However if a * partition is reassigned it may want to automatically trigger a flush of this cache, before the new owner takes over * consumption. * <p>
