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

See Changes: [me] KAFKA-7431: Clean up connect unit tests -- [...truncated 2.33 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldProcessConsumerRecordList[Eo

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

See Changes: [me] KAFKA-7431: Clean up connect unit tests -- [...truncated 2.73 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldFailIfKeyIsDifferentForCo

[jira] [Created] (KAFKA-7605) Flaky Test `SaslMultiMechanismConsumerTest.testCoordinatorFailover`

Jason Gustafson created KAFKA-7605: -- Summary: Flaky Test `SaslMultiMechanismConsumerTest.testCoordinatorFailover` Key: KAFKA-7605 URL: https://issues.apache.org/jira/browse/KAFKA-7605 Project: Kafka

[jira] [Created] (KAFKA-7604) Flaky Test `ConsumerCoordinatorTest.testRebalanceAfterTopicUnavailableWithPatternSubscribe`

Jason Gustafson created KAFKA-7604: -- Summary: Flaky Test `ConsumerCoordinatorTest.testRebalanceAfterTopicUnavailableWithPatternSubscribe` Key: KAFKA-7604 URL: https://issues.apache.org/jira/browse/KAFKA-7604

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

See Changes: [me] KAFKA-7560; PushHttpMetricsReporter should not convert metric value to -- [...truncated 1.47 MB...] kafka.tools.ConsoleConsumerTest > shouldStopWhenOutpu

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

See Changes: [me] KAFKA-7560; PushHttpMetricsReporter should not convert metric value to -- [...truncated 800.34 KB...] kafka.server.MetadataRequestTest > testControllerI

Re: [VOTE] - KIP-213 Support non-key joining in KTable

Bumping this thread, as per convention - 1 On Fri, Nov 2, 2018 at 8:22 AM Adam Bellemare wrote: > As expected :) But still, thanks none-the-less! > > On Fri, Nov 2, 2018 at 3:36 AM Jan Filipiak > wrote: > >> reminder >> >> On 30.10.2018 15:47, Adam Bellemare wrote: >> > Hi All >> > >> > I would

[jira] [Resolved] (KAFKA-6262) KIP-232: Detect outdated metadata by adding ControllerMetadataEpoch field

[ https://issues.apache.org/jira/browse/KAFKA-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dong Lin resolved KAFKA-6262. - Resolution: Duplicate The design in this Jira has been moved to KIP-320. > KIP-232: Detect outdated meta

[jira] [Created] (KAFKA-7603) Producer should negotiate message format version with broker

Dong Lin created KAFKA-7603: --- Summary: Producer should negotiate message format version with broker Key: KAFKA-7603 URL: https://issues.apache.org/jira/browse/KAFKA-7603 Project: Kafka Issue Type:

Observer

Addition to my previous e-mail ...   I think, that there should be Observer pattern. I think, that Consumer interface is Observer interface with method update (i do not know how this method is called in Consumer). I have two ideas, which classes could be concrete observers. First idea is, that c

Re: [VOTE] 2.0.1 RC0

+1 (binding) Checked source build and unit tests. Ran quickstart with source and binary. Thank you for managing the release, Manikumar! Regards, Rajini On Wed, Nov 7, 2018 at 6:18 PM Gwen Shapira wrote: > +1 (binding) > > Checked signatures, build and quickstart. > > Thank you for managing t

Re: [VOTE] 2.0.1 RC0

+1 (binding) Checked signatures, build and quickstart. Thank you for managing the release, Mani! On Thu, Oct 25, 2018 at 7:29 PM Manikumar wrote: > > Hello Kafka users, developers and client-developers, > > This is the first candidate for release of Apache Kafka 2.0.1. > > This is a bug fix re

Build failed in Jenkins: kafka-2.1-jdk8 #52

See Changes: [me] KAFKA-7560; PushHttpMetricsReporter should not convert metric value to -- [...truncated 427.34 KB...] kafka.server.KafkaConfigTest > testCaseInsensitiveList

design patterns

Hi can you help me identify some design patterns in the code apache/kafka ? Thanks   Mrkvica

Re: [VOTE] 2.0.1 RC0

Since that was just a system tests fix, it doesn't seem to require another RC. We just need a couple more votes. I'll ping some PMC members. Ismael On Wed, Nov 7, 2018 at 5:01 AM Manikumar wrote: > KAFKA-7581, KAFKA-7579 are not blockers for 2.0.1 release. KAFKA-7579 got > fixed on 2.0 branch.

Re: [VOTE] 2.0.1 RC0

Thanks Manikumar, I think you need to make a call on KAFKA-7579 as release manager and push this through. Eno On Wed, Nov 7, 2018 at 1:01 PM Manikumar wrote: > KAFKA-7581, KAFKA-7579 are not blockers for 2.0.1 release. KAFKA-7579 got > fixed on 2.0 branch. > This can be part of 2.0.1, if we are

[jira] [Resolved] (KAFKA-7560) PushHttpMetricsReporter should not convert metric value to double

[ https://issues.apache.org/jira/browse/KAFKA-7560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ewen Cheslack-Postava resolved KAFKA-7560. -- Resolution: Fixed Fix Version/s: 2.1.0 2.2.0 Issue re

Re: [VOTE] 2.0.1 RC0

KAFKA-7581, KAFKA-7579 are not blockers for 2.0.1 release. KAFKA-7579 got fixed on 2.0 branch. This can be part of 2.0.1, if we are going with another RC. We need couple of more PMC votes to pass this vote thread. On Wed, Nov 7, 2018 at 4:43 PM Eno Thereska wrote: > Two JIRAs are still marked a

[jira] [Resolved] (KAFKA-7579) System Test Failure - security_test.SecurityTest.test_client_ssl_endpoint_validation_failure

[ https://issues.apache.org/jira/browse/KAFKA-7579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar resolved KAFKA-7579. -- Resolution: Fixed Fix Version/s: 2.1.0 This is fixed via KAFKA-7561. > System Test Failure -

Re: [VOTE] 2.0.1 RC0

Two JIRAs are still marked as blockers, although it's not clear to me if they really are. Any update? Thanks Eno On Thu, Nov 1, 2018 at 5:10 PM Manikumar wrote: > We were waiting for the system test results. There were few failures: > KAFKA-7579, KAFKA-7559, KAFKA-7561 > they are not blockers f

Re: [VOTE] KIP-374: Add '--help' option to all available Kafka CLI commands

+1 (non-binding) Thanks for this KIP. Viktor On Wed, Oct 31, 2018 at 2:43 PM Srinivas Reddy wrote: > Hi All, > > I would like to call for a vote on KIP-374: > https://cwiki.apache.org/confluence/x/FgSQBQ > > Summary: > Currently, the '--help' option is recognized by some Kafka commands > but n

Re: [DISCUSS] KIP-345: Reduce multiple consumer rebalances by specifying member id

I took a quick pass of the proposal. First I would say it's a very brilliant initiative from Konstantine and Confluent folks. To draft up a proposal like this needs deep understanding of the rebalance protocol! I summarized some thoughts here. Overall the motivations of the two proposals align