chia7712 commented on code in PR #22270:
URL: https://github.com/apache/kafka/pull/22270#discussion_r3312657008


##########
clients/src/main/java/org/apache/kafka/clients/consumer/ConsumerRebalanceListener.java:
##########
@@ -154,18 +171,45 @@ public interface ConsumerRebalanceListener {
      * necessary to catch these exceptions and re-attempt to wakeup or 
interrupt the consumer thread.
      *
      * @param partitions The list of partitions that were assigned to the 
consumer and now need to be revoked. This will
-     *                  include the full assignment under the Classic/Eager 
protocol, given that it revokes all partitions.
+     *                   include the full assignment under the Classic/Eager 
protocol, given that it revokes all partitions.
      *                   It will only include the subset to revoke under the 
Classic/Cooperative and Consumer protocols.
      * @throws org.apache.kafka.common.errors.WakeupException If raised from a 
nested call to {@link KafkaConsumer}
      * @throws org.apache.kafka.common.errors.InterruptException If raised 
from a nested call to {@link KafkaConsumer}
      */
-    void onPartitionsRevoked(Collection<TopicPartition> partitions);
+    default void onPartitionsRevoked(Collection<TopicPartition> partitions) {}

Review Comment:
   > I've introduced a new ConsumerAwareRebalanceListener 
[here](https://github.com/apache/kafka/pull/22270/changes#diff-7b1d23741295e3d562a3da8f6e7378abbf4332b1c2766678f667d9840d119ce9R39)
   
   That's not what I meant. What I'm proposing is a new public super-interface 
for the end-users to implement. By extracting a public super-interface, we can 
keep the new API completely clean for new users, while preserving 100% source 
compatibility for legacy Scala users



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to