Jenkins build is back to normal : kafka-2.0-jdk8 #243

See

Build failed in Jenkins: kafka-2.2-jdk8 #77

See Changes: [github] KAFKA-8157: fix the incorrect usage of segment.index.bytes (2.2) (#6547) -- [...truncated 2.69 MB...] kafka.controller.PartitionLeaderElectionAlgorithm

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

See -- [...truncated 545 B...] > git config remote.origin.url https://github.com/apache/kafka.git # timeout=10 Fetching upstream changes from https://github.com/apache/kafka.git > git -

[jira] [Resolved] (KAFKA-8058) ConnectRestExtensionContext does not return list of connectors from its ConnectClusterState

[ https://issues.apache.org/jira/browse/KAFKA-8058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Randall Hauch resolved KAFKA-8058. -- Resolution: Fixed > ConnectRestExtensionContext does not return list of connectors from its >

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

See -- [...truncated 545 B...] > git config remote.origin.url https://github.com/apache/kafka.git # timeout=10 Fetching upstream changes from https://github.com/apache/kafka.git > git -

Re: [DISCUSS] KIP-440: Extend Connect Converter to support headers

Hello Randall, Thanks for your suggestion, I've just updated the KIP. Let me know what you think! On 2019/04/02 20:12:56, Randall Hauch wrote: > Thanks for the submission, Yaroslav -- and for building on the suggestion> > of Jeremy C in https://issues.apache.org/jira/browse/KAFKA-7273. This is a

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

See -- [...truncated 545 B...] > git config remote.origin.url https://github.com/apache/kafka.git # timeout=10 Fetching upstream changes from https://github.com/apache/kafka.git > git -

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

See -- [...truncated 545 B...] > git config remote.origin.url https://github.com/apache/kafka.git # timeout=10 Fetching upstream changes from https://github.com/apache/kafka.git > git -

Jenkins build is back to normal : kafka-2.2-jdk8 #78

See

Jenkins build is back to normal : kafka-2.1-jdk8 #159

See

Re: [DISCUSS] KIP-435: Incremental Partition Reassignment

Hi George, As Jason was saying, it seems like there are two directions we could go here: an external system handling batching, and the controller handling batching. I think the controller handling batching would be better, since the controller has more information about the state of the system

Re: [DISCUSS] KIP-424: Allow suppression of intermediate events based on wall clock time

On 2019/03/11 21:39:18, John Roesler wrote: > Regarding flushing on shutdown, can you elaborate of the motivation for > doing so? I'm not in any way attached to this idea if you think it's not any additional trouble. It wasn't obvious to me how you would store the "wall clock time last flushed

Jenkins build is back to normal : kafka-trunk-jdk8 #3520

See

Re: [DISCUSS] KIP-435: Incremental Partition Reassignment

Good discussion about where we should do batching. I think if there is a clear great way to batch, then it makes a lot of sense to just do it once. However, if we think there is scope for experimenting with different approaches, then an API that tools can use makes a lot of sense. They can experime