Jenkins build is back to normal : kafka-2.4-jdk8 #80

See

Build failed in Jenkins: kafka-trunk-jdk11 #970

See Changes: [rhauch] KAFKA-9051: Prematurely complete source offset read requests for stopped -- [...truncated 2.74 MB...] org.apache.kafka.streams.scala.StreamToTable

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

See Changes: [rhauch] KAFKA-9051: Prematurely complete source offset read requests for stopped -- [...truncated 2.74 MB...] org.apache.kafka.streams.test.ConsumerRecordF

[jira] [Created] (KAFKA-9215) Mirrormaker 2.0 (connect-standalone.sh)

Jan Arve Sundt created KAFKA-9215: - Summary: Mirrormaker 2.0 (connect-standalone.sh) Key: KAFKA-9215 URL: https://issues.apache.org/jira/browse/KAFKA-9215 Project: Kafka Issue Type: Wish

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

See

Build failed in Jenkins: kafka-2.3-jdk8 #137

See Changes: [rhauch] KAFKA-9051: Prematurely complete source offset read requests for stopped -- [...truncated 2.92 MB...] kafka.security.auth.ResourceTypeTest > testFromS

[VOTE] 2.4.0 RC1

Hello Kafka users, developers and client-developers, This is the second candidate for release of Apache Kafka 2.4.0. This release includes many new features, including: - Allow consumers to fetch from closest replica - Support for incremental cooperative rebalancing to the consumer rebalance prot

Re: Subject: [VOTE] 2.2.2 RC2

Thanks for reviewing this release candidate! This vote passes with 9 +1 votes (3 bindings) and no 0 or -1 votes. +1 votes PMC Members: * Matthias J. Sax * Gwen Shapira * Jason Gustafson Committers: * Mickael Maison * David Arthur * Bill Bejeck Community: * Eric Lalonde * Satish Duggana * Jakub

[jira] [Created] (KAFKA-9216) Enforce connect internal topic configuration at startup

Randall Hauch created KAFKA-9216: Summary: Enforce connect internal topic configuration at startup Key: KAFKA-9216 URL: https://issues.apache.org/jira/browse/KAFKA-9216 Project: Kafka Issue T

Jenkins build is back to normal : kafka-trunk-jdk11 #971

See

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

Hello all, I've refactored the KIP to remove implementing asynchronous metadata fetching in the producer during send(). It's now exclusively focused on reducing the topic metadata fetch payload and proposes adding a new configuration flag to control topic expiry behavior. Please take a look when p

Re: [DISCUSS] KIP-533: Add default api timeout to AdminClient

This seems not very controversial, so I will go ahead and move to a vote in the next couple days. Thanks, Jason On Wed, Nov 13, 2019 at 10:23 AM Jason Gustafson wrote: > Hey Colin, > > Thanks for the suggestions. I've clarified the use of the API overrides > and the request timeout. > > I think

Build failed in Jenkins: kafka-trunk-jdk11 #972

See Changes: [github] Revert "KAFKA-9165: Fix jersey warnings in Trogdor (#7669)" (#7721) -- [...truncated 2.75 MB...] org.apache.kafka.streams.TopologyTestDriverTest >

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

See

RE: [DISCUSS] KIP-280: Enhanced log compaction

Hi Gouzhang & Jun, Thanks for the detailed on the scenarios. #51 => thanks for the details Gouzhang with example. Does followers won't be sync'ing LEO as well with leader? If yes, keeping last record always (without compaction for non-offset scenarios) would work and this needed only if the n

Re: [DISCUSS] KIP-526: Reduce Producer Metadata Lookups for Large Number of Topics

I think it's ok, and you can add another issue about `asynchronous metadata` if `topic expiry` is not enough. On Thu, Nov 21, 2019 at 6:20 AM Brian Byrne wrote: > Hello all, > > I've refactored the KIP to remove implementing asynchronous metadata > fetching in the producer during send(). It's n

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

See Changes: [github] Revert "KAFKA-9165: Fix jersey warnings in Trogdor (#7669)" (#7721) [github] KAFKA-8986: Allow null as a valid default for tagged fields. (#7585) -

Re: [DISCUSS] KIP-547: Extend ConsumerInterceptor to allow modification of Consumer Commits

Hi, Eric what's the use of this method? I reviewed the code and couldn't find much of the metadata's usage, and I find its usage trivial. On Tue, Nov 19, 2019 at 3:19 AM Eric Azama wrote: > Hi all, > > I'd like to open discussion on KIP-547: Extend ConsumerInterceptor to allow > modification of

Re: [DISCUSS] KIP-547: Extend ConsumerInterceptor to allow modification of Consumer Commits

Hi Deng, It's similar to Record Headers in that the metadata isn't used within Kafka itself. The intended purpose of the Metadata is to store additional information such as what application instance made the commit. Most of the value is going to be in giving organizations the ability to do things

Jenkins build is back to normal : kafka-trunk-jdk11 #973

See

[jira] [Created] (KAFKA-9217) Partial partition's log-end-offset is zero

lisen created KAFKA-9217: Summary: Partial partition's log-end-offset is zero Key: KAFKA-9217 URL: https://issues.apache.org/jira/browse/KAFKA-9217 Project: Kafka Issue Type: Bug Components