[jira] [Updated] (KAFKA-3043) Replace request.required.acks with acks in docs

[ https://issues.apache.org/jira/browse/KAFKA-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gwen Shapira updated KAFKA-3043: Resolution: Fixed Fix Version/s: (was: 0.9.0.0) 0.9.1.0 Stat

[jira] [Commented] (KAFKA-3043) Replace request.required.acks with acks in docs

[ https://issues.apache.org/jira/browse/KAFKA-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15072074#comment-15072074 ] ASF GitHub Bot commented on KAFKA-3043: --- Github user asfgit closed the pull request

[GitHub] kafka pull request: KAFKA-3043: Replace request.required.acks with...

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/716 --- 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 enabl

Re: [DISCUSS] KIP-36 - Rack aware replica assignment

Added the rolling upgrade instruction in the KIP, similar to those in 0.9.0 release notes. On Wed, Dec 16, 2015 at 11:32 AM, Allen Wang wrote: > Hi Jun, > > The reason that TopicMetadataResponse is not included in the KIP is that > it currently is not version aware . So we need to introduce vers

Build failed in Jenkins: kafka-trunk-jdk7 #927

See Changes: [cshapi] MINOR: Improve document of MirrorMaker -- [...truncated 1411 lines...] kafka.log.LogTest > testTruncateTo PASSED kafka.log.LogTest > testCleanShutdownFile PASSED kafka.lo

Build failed in Jenkins: kafka-trunk-jdk8 #258

See Changes: [cshapi] MINOR: Improve document of MirrorMaker -- [...truncated 1419 lines...] kafka.log.LogCleanerIntegrationTest > cleanerTest[3] PASSED kafka.log.LogTest > testParseTopicPartit

[GitHub] kafka pull request: MINOR: Improve document of MirrorMaker

Github user asfgit closed the pull request at: https://github.com/apache/kafka/pull/717 --- 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 enabl