GitHub user vahidhashemian reopened a pull request:

    https://github.com/apache/kafka/pull/1726

    KAFKA-4033: KIP-70: Revise Partition Assignment Semantics on New Consumer's 
Subscription Change

    This PR changes topic subscription semantics so a change in subscription 
does not immediately cause a rebalance.
    Instead, the next poll or the next scheduled metadata refresh will update 
the assigned partitions.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/vahidhashemian/kafka KAFKA-4033

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/1726.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1726
    
----
commit 09d35a5f8b5b91c9d71de345c14ccf8c8ef21876
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2016-08-22T18:45:52Z

    KAFKA-4033: KIP-70: Revise Partition Assignment Semantics on New Consumer's 
Subscription Change
    
    This PR changes topic subscription semantics so a change in subscription 
does not immediately cause a rebalance.
    Instead, the next poll or the next scheduled metadata refresh will update 
the assigned partitions.

commit e26a42fff83ea8a3d997ad97d5cc2b5704f1e62b
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2016-08-22T23:29:48Z

    Unit test for subscription change

commit cc9c4c4750addbc7a99588ff69e669b96a18d361
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2016-08-24T06:22:05Z

    Clean up KafkaConsumerTest.java and add reusable methods

commit f60fb52a702a6bcb854e9560548174fc5ad86730
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date:   2016-08-26T00:23:22Z

    Fix unsubscribe semantics and update unit tests

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to