…artition info.

Author: Dong Lin <lindong28@gmail.com>
Author: Dong Lin <lindong@cis.upenn.edu>

Reviewers: Jason Gustafson, Ismael Juma, Guozhang Wang

Closes apache#118 from lindong28/KAFKA-2390

…ition Topic

We now write to the channel with an empty buffer when
there are pending bytes remaining and all data has been
sent.

Author: Ismael Juma <ismael@juma.me.uk>

Reviewers: Sriharsha Chintalapani <schintalapani@hortonworks.com>, Ben Stopford <benstopford@gmail.com>, Jun Rao <junrao@gmail.com>

Closes apache#236 from ijuma/kafka-2576-ssl-multi-partition-topic-hang

…y created when two zookeeper sessions are established in a very short period of time

This is a patch to get around the problem discussed in the KAFKA-1387 jira. The tests are not passing in my box when I run them all, but they do pass when I run them individually, which indicates that there is something leaking from a test to the next. I still need to work this out and also work on further testing this. I wanted to open this PR now so that it can start getting reviewed.

Author: flavio junqueira <fpj@apache.org>
Author: fpj <fpj@apache.org>
Author: Flavio Junqueira <fpj@apache.org>

Reviewers: Ismael Juma <ismael@juma.me.uk>, Guozhang Wang <wangguoz@gmail.com>, Jun Rao <junrao@gmail.com>

Closes apache#178 from fpj/1387

… 0.9.0.0

Simplified the logic to choose the default fix version. We just hardcode
it for `trunk` and try to compute it based on the branch name for the
rest.

Removed logic that tries to handle forked release branches as it
seems to be specific to how the Spark project handles their JIRA.

Author: Ismael Juma <ismael@juma.me.uk>

Reviewers: Guozhang Wang

Closes apache#238 from ijuma/kafka-2548-merge-pr-tool-4-segment-fix-version

Updated the version from 0.8.3 to 0.9.0. in ApiVersion.  Also updated in gradle.propeties.

Author: Manikumar reddy O <manikumar.reddy@gmail.com>

Reviewers: Ismael Juma, Gwen Shapira

Closes apache#237 from omkreddy/KAFKA-2554

Author: Dong Lin <lindong28@gmail.com>

Reviewers: Jason Gustafson, Guozhang Wang

Closes apache#239 from lindong28/KAFKA-2390-followup

Author: Ewen Cheslack-Postava <me@ewencp.org>

Reviewers: Gwen Shapira, James Cheng

Closes apache#202 from ewencp/kafka-2373-copycat-distributed-offset

Author: Ashish Singh <asingh@cloudera.com>

Reviewers: Ewen Cheslack-Postava, Gwen Shapira

Closes apache#231 from SinghAsDev/KAFKA-2571

Author: Jason Gustafson <jason@confluent.io>

Reviewers: Gwen Shapira

Closes apache#240 from hachikuji/KAFKA-2579

… commit

Author: Jason Gustafson <jason@confluent.io>

Reviewers: Onur Karaman, Guozhang Wang

Closes apache#243 from hachikuji/KAFKA-2409

…ack's commitSync

hachikuji ewencp I found this problem when adding new consumer to mirror maker which commits offset in the rebalance callback. It is not clear to me why we are triggering rebalance for commitSync() and fetchCommittedOffset(). Can you help review to see if I miss something?

Regarding commitSync, After each poll() the partitions will be either assigned to a consumer or it will be already revoked. As long as user is using internal offset map, the offset map will always be valid. i.e. the offset map will always only contain the assigned partitions when commitSync is called. Hence there is no need to trigger a rebalance in commitSync().

The same guarantee also apply to fetchCommittedOffset(), isn't the only requirement is to ensure we know the coordinator?

Another related issue is that today the IllegalGenerationIdException is a bit confusing. When we receive an IllegalGenerationIdException from heartbeat, we need to use that same generation Id to commit offset and the coordinator will take it. So the generation ID was not really illegal. I will file a ticket for this issue.

Author: Jiangjie Qin <becket.qin@gmail.com>

Reviewers: Jason Gustafson, Guozhang Wang

Closes apache#221 from becketqin/KAFKA-2555