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

See Changes: [wangguoz] KAFKA-9277:move all group state transition rules into their states [jason] KAFKA-9232; Coordinator new member timeout does not work for JoinGroup

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

See

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

See

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

See Changes: [jason] KAFKA-9307; Make transaction metadata loading resilient to previous -- [...truncated 2.95 MB...] kafka.zk.KafkaZkClientTest >

Build failed in Jenkins: kafka-2.4-jdk8 #117

See Changes: [bill] fix rows (#7837) -- [...truncated 8.42 MB...] org.apache.kafka.streams.test.OutputVerifierTest > shouldNotAllowNullExpectedRecordForCompareValue

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

See Changes: [jason] KAFKA-9232; Coordinator new member timeout does not work for JoinGroup -- [...truncated 924.02 KB...] kafka.log.ProducerStateManagerTest >

[jira] [Resolved] (KAFKA-9232) Coordinator new member heartbeat completion does not work for JoinGroup v3

[ https://issues.apache.org/jira/browse/KAFKA-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9232. Fix Version/s: 2.4.1 2.3.2 2.2.3

Build failed in Jenkins: kafka-2.2-jdk8-old #198

See Changes: [jason] KAFKA-9307; Make transaction metadata loading resilient to previous [jason] KAFKA-9232; Coordinator new member timeout does not work for JoinGroup

[jira] [Resolved] (KAFKA-9307) Transaction coordinator could be left in unknown state after ZK session timeout

[ https://issues.apache.org/jira/browse/KAFKA-9307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-9307. Resolution: Fixed > Transaction coordinator could be left in unknown state after ZK

[jira] [Resolved] (KAFKA-9277) move all group state transition rules into their states

[ https://issues.apache.org/jira/browse/KAFKA-9277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-9277. -- Fix Version/s: 2.5.0 Resolution: Fixed > move all group state transition rules into

[jira] [Created] (KAFKA-9331) Add option to terminate application when StreamThread(s) die

Michael Bingham created KAFKA-9331: -- Summary: Add option to terminate application when StreamThread(s) die Key: KAFKA-9331 URL: https://issues.apache.org/jira/browse/KAFKA-9331 Project: Kafka

[jira] [Created] (KAFKA-9330) Calling AdminClient.close in the AdminClient completion callback causes deadlock

Vikas Singh created KAFKA-9330: -- Summary: Calling AdminClient.close in the AdminClient completion callback causes deadlock Key: KAFKA-9330 URL: https://issues.apache.org/jira/browse/KAFKA-9330 Project:

Re: Proposal for EmbeddedKafkaCluster: Support JUnit 5 Extension in addition to JUnit 4 Rule

Hi John, Thanks for your feedback and offer. Yes, I would be interested in proposing this feature. (will be off-line for a few days so it would be early next year :) Any help regarding the process and possible KIP would be appreciated. Cheers, Matthias

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

See Changes: [bbejeck] fix rows (#7837) -- [...truncated 2.79 MB...] org.apache.kafka.streams.TopologyTestDriverTest > shouldPunctuateIfWallClockTimeAdvances[Eos

Re: [DISCUSS] KIP-515: Enable ZK client to use the new TLS supported authentication

Hi everyone. Let's get this discussion going again now that Kafka 2.4 with Zookeeper 3.5.6 is out. First, regarding the KIP number, the other KIP that was using this number moved to KIP 534, so KIP 515 remains the correct number for this discussion. I've updated the Kafka Improvement Proposal

[jira] [Resolved] (KAFKA-9326) Kafka Connect JSON Converter results in data loss when additional fields apart from provided JSON schema is present in the payload

[ https://issues.apache.org/jira/browse/KAFKA-9326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rameshkrishnan muthusamy resolved KAFKA-9326. - Resolution: Invalid > Kafka Connect JSON Converter results in data loss

[jira] [Created] (KAFKA-9329) KafkaController::replicasAreValid should return error

Vikas Singh created KAFKA-9329: -- Summary: KafkaController::replicasAreValid should return error Key: KAFKA-9329 URL: https://issues.apache.org/jira/browse/KAFKA-9329 Project: Kafka Issue Type:

Please give a link where I can explain myself what this can be ...

I'am reading the folowing code : ... KTable wordCounts = textLines .flatMapValues(textLine -> Arrays.asList(textLine.toLowerCase().split("\\W+"))) .groupBy((key, word) -> word) .count(Materialized.>as("counts-store")); ... I do not understand

[jira] [Created] (KAFKA-9328) Move MirrorMaker 2.0 documentation to site-docs

Gwen Shapira created KAFKA-9328: --- Summary: Move MirrorMaker 2.0 documentation to site-docs Key: KAFKA-9328 URL: https://issues.apache.org/jira/browse/KAFKA-9328 Project: Kafka Issue Type:

Re: MirrorMaker 2.0 Documentation

OK, awesome :) I just wanted to make sure there are no objections before opening the JIRA, since discussions are easier on the mailing list. On Mon, Dec 23, 2019 at 5:01 PM Ryanne Dolan wrote: > > Gwen, no one is hiding anything. Please follow up your JIRAs with PRs and > I'm sure we can get the

Re: MirrorMaker 2.0 Documentation

Gwen, no one is hiding anything. Please follow up your JIRAs with PRs and I'm sure we can get the site updated. Ryanne On Mon, Dec 23, 2019, 8:38 AM Gwen Shapira wrote: > There's nothing preventing us from updating the site-docs now to make them > match the 2.4 release better (I just opened

Re: MirrorMaker 2.0 Documentation

There's nothing preventing us from updating the site-docs now to make them match the 2.4 release better (I just opened few JIRA for additional docs). Is there a reason why we want to hide MirrorMaker 2.0 until next release? For example, is it unstable? Do you expect interfaces or tools to

Re: MirrorMaker 2.0 Documentation

Hey Gwen, per the KIP, the depreciation plan will take a few releases. Copied here: Phase 1 (targeting next Apache Kafka release): All MirrorMaker 2.0 Java code is added to ./connect/mirror/. Phase 2 (subsequent release): Legacy MirrorMaker Scala code is deprecated, but kept in place. Sample MM2

[jira] [Created] (KAFKA-9327) GroupMetadata metrics are not documented

Gwen Shapira created KAFKA-9327: --- Summary: GroupMetadata metrics are not documented Key: KAFKA-9327 URL: https://issues.apache.org/jira/browse/KAFKA-9327 Project: Kafka Issue Type: Improvement

[jira] [Created] (KAFKA-9326) Kafka Connect JSON Converter results in data loss when additional fields apart from provided JSON schema is present in the payload

rameshkrishnan muthusamy created KAFKA-9326: --- Summary: Kafka Connect JSON Converter results in data loss when additional fields apart from provided JSON schema is present in the payload Key: KAFKA-9326

Re: Permission to create KIP

Do you have a user name on Apache wiki? Let me know what it is, and I'll give you edit permissions so you can create a KIP On Mon, Dec 23, 2019, 7:58 AM Anbarasan r wrote: > Hello Team, > > I would like to work on a long-pending feature > https://issues.apache.org/jira/browse/KAFKA-566. > I

[jira] [Created] (KAFKA-9325) Document Follower Fetch

Gwen Shapira created KAFKA-9325: --- Summary: Document Follower Fetch Key: KAFKA-9325 URL: https://issues.apache.org/jira/browse/KAFKA-9325 Project: Kafka Issue Type: Improvement

MirrorMaker 2.0 Documentation

Hey, I was surprised to discover that MirrorMaker 2.0 (part of 2.4 release), is not mentioned at all in our documentation (https://kafka.apache.org/documentation/). Ryanne Dolan was kind enough to point me to the documentation for this feature