Re: [DISCUSS] KIP-618: Atomic commit of source connector records and offsets

Hey Chris, Thank you for the proposal. Few questions / comments: 0. It may be worth pointing out in the motivation section that source-connector exactly once is more important than sink connector exactly once, since many target systems will have unique key constraint mechanisms that will prevent

[jira] [Created] (KAFKA-12352) Improve debuggability with continuous consumer rebalances

Guozhang Wang created KAFKA-12352: - Summary: Improve debuggability with continuous consumer rebalances Key: KAFKA-12352 URL: https://issues.apache.org/jira/browse/KAFKA-12352 Project: Kafka

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #496

See Changes: [github] MINOR: Remove redundant log close in `KafkaRaftClient` (#10168) -- [...truncated 7.11 MB...]

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #527

See Changes: [github] MINOR: Remove redundant log close in `KafkaRaftClient` (#10168) -- [...truncated 3.64 MB...] SocketServerTest >

Re: [DISCUSS] KIP-706: Add method "Producer#produce" to return CompletionStage instead of Future

Currently the community is busy with merging all the KIP-500 related work into trunk for the 2.8 release so no committer reply 廊. Not very sure, but I find that org.apache.kafka.clients.consumer.internals.RequestFuture Is also similar to CompletableFuture, do we have plan to replace

[jira] [Resolved] (KAFKA-12351) Fix misleading max.request.size behavior

[ https://issues.apache.org/jira/browse/KAFKA-12351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-12351. - Resolution: Duplicate > Fix misleading max.request.size behavior >

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #552

See Changes: [github] MINOR: Remove redundant log close in `KafkaRaftClient` (#10168) -- [...truncated 3.66 MB...] ApiVersionTest > testApply() STARTED

Build failed in Jenkins: Kafka » kafka-2.8-jdk8 #23

See Changes: [Jason Gustafson] MINOR: Remove redundant log close in `KafkaRaftClient` (#10168) -- [...truncated 1.80 MB...] KafkaConsumerTest >

[jira] [Created] (KAFKA-12351) Fix misleading max.request.size behavior

Jason Gustafson created KAFKA-12351: --- Summary: Fix misleading max.request.size behavior Key: KAFKA-12351 URL: https://issues.apache.org/jira/browse/KAFKA-12351 Project: Kafka Issue Type:

Jenkins build is back to normal : Kafka » kafka-2.7-jdk8 #124

See

Build failed in Jenkins: Kafka » kafka-trunk-jdk15 #551

See Changes: [github] MINOR: AbstractCoordinator should log with its subclass (#10149) [github] MINOR: apply Utils.isBlank to code base (#10124) --

Build failed in Jenkins: Kafka » kafka-trunk-jdk8 #495

See Changes: [github] KAFKA-12335 Upgrade junit from 5.7.0 to 5.7.1 (#10145) [github] MINOR: Enhance the documentation with the metric unit which is milliseconds (#10148) [github] MINOR:

[GitHub] [kafka-site] showuon opened a new pull request #332: KAFKA-12350: correct the wrong default value in doc

showuon opened a new pull request #332: URL: https://github.com/apache/kafka-site/pull/332 Correct the wrong default value. ref: https://github.com/apache/kafka/pull/10165 This is an automated message from the Apache Git

Build failed in Jenkins: Kafka » kafka-trunk-jdk11 #526

See Changes: [github] KAFKA-12276: Add the quorum controller code (#10070) [github] KAFKA-12335 Upgrade junit from 5.7.0 to 5.7.1 (#10145) [github] MINOR: Enhance the documentation with the metric

[jira] [Created] (KAFKA-12350) document about refresh.topics.interval.seconds default value is not right

superheizai created KAFKA-12350: --- Summary: document about refresh.topics.interval.seconds default value is not right Key: KAFKA-12350 URL: https://issues.apache.org/jira/browse/KAFKA-12350 Project: