[jira] [Resolved] (KAFKA-18599) Remove optional ForwardingManager in ApiVersionManager

[ https://issues.apache.org/jira/browse/KAFKA-18599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ismael Juma resolved KAFKA-18599. - Resolution: Fixed > Remove optional ForwardingManager in ApiVersionManager > ---

[jira] [Created] (KAFKA-18619) New consumer topic metadata events should set requireMetadata flag

Lianet Magrans created KAFKA-18619: -- Summary: New consumer topic metadata events should set requireMetadata flag Key: KAFKA-18619 URL: https://issues.apache.org/jira/browse/KAFKA-18619 Project: Kafka

[jira] [Resolved] (KAFKA-18229) Move configs out of "kraft" directory

[ https://issues.apache.org/jira/browse/KAFKA-18229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-18229. Resolution: Fixed > Move configs out of "kraft" directory > --

[jira] [Created] (KAFKA-18620) Remove UnifiedLog#legacyFetchOffsetsBefore

TengYao Chi created KAFKA-18620: --- Summary: Remove UnifiedLog#legacyFetchOffsetsBefore Key: KAFKA-18620 URL: https://issues.apache.org/jira/browse/KAFKA-18620 Project: Kafka Issue Type: Sub-task

[jira] [Created] (KAFKA-18621) Add StreamsCoordinatorRecordHelpers

Lucas Brutschy created KAFKA-18621: -- Summary: Add StreamsCoordinatorRecordHelpers Key: KAFKA-18621 URL: https://issues.apache.org/jira/browse/KAFKA-18621 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-17853) Console share consumer is not terminated immediately

[ https://issues.apache.org/jira/browse/KAFKA-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-17853. --- Resolution: Cannot Reproduce > Console share consumer is not terminated immediately > --

[jira] [Resolved] (KAFKA-18519) Remove Json.scala , cleanup AclEntry.scala

[ https://issues.apache.org/jira/browse/KAFKA-18519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-18519. Fix Version/s: 4.0.0 Resolution: Fixed > Remove Json.scala , cleanup AclEntry.scala

Re: [DISCUSS] Rename use of term "broker" in DescribeClusterResponse

Hi Anton, I think this is a good idea given that the change is binary-compatible and it makes it more clear that both brokers and controllers are represented in the response. Personally, I think this should be a very small KIP so that we can properly review and sign off on making the change. I kno

[DISCUSS] Rename use of term "broker" in DescribeClusterResponse

Hello, The DescribeClusterResponse protocol entity is used for modeling both brokers and controllers, however, naming of fields in this entity has not been updated to reflect this fact and causes some confusion. Renaming fields, and documentation is not breaking API compatibility, and I suggest i

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.9 #153

See

[jira] [Resolved] (KAFKA-18595) Remove AuthorizerUtils#sessionToRequestContext

[ https://issues.apache.org/jira/browse/KAFKA-18595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-18595. --- Resolution: Fixed The PR has been reviewed and merged both in trunk and 4.0 > Remove Author

[jira] [Resolved] (KAFKA-18598) Remove ControllerMetadataMetrics zk related Metrics

[ https://issues.apache.org/jira/browse/KAFKA-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christo Lolov resolved KAFKA-18598. --- Resolution: Fixed The PR has been reviewed and merged both in trunk and in 4.0 > Remove Con

[jira] [Created] (KAFKA-18625) consumer client could get duplicated records if assigned partitions change quickly

Jun Rao created KAFKA-18625: --- Summary: consumer client could get duplicated records if assigned partitions change quickly Key: KAFKA-18625 URL: https://issues.apache.org/jira/browse/KAFKA-18625 Project: Kaf

[jira] [Created] (KAFKA-18624) Add validation for advertised listeners

Divij Vaidya created KAFKA-18624: Summary: Add validation for advertised listeners Key: KAFKA-18624 URL: https://issues.apache.org/jira/browse/KAFKA-18624 Project: Kafka Issue Type: Improveme

Re: [DISCUSS] Changing which commit we build in PRs

This change will help with test time since it will increase cache hits for the Gradle test tasks. For example, if your PR only changes streams code you should ideally not see other modules get re-tested (unless they are downstream dependencies of :streams). I've learned from ASF Infra that merge q

Re: [DISCUSS] Changing which commit we build in PRs

> > This change will help with test time since it will increase cache hits for > the Gradle test tasks. For example, if your PR only changes streams code > you should ideally not see other modules get re-tested (unless they are > downstream dependencies of :streams). Ok thanks for clarifying. But

[jira] [Resolved] (KAFKA-18518) Add Streams Rebalance interface

[ https://issues.apache.org/jira/browse/KAFKA-18518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-18518. --- Resolution: Fixed > Add Streams Rebalance interface > --- > >

Re: [DISCUSS] Changing which commit we build in PRs

David, just to make sure I understand, are you saying this will help with the actual test runtime, or only the compile time of the build? Just wondering because I've personally never found the compile times to be a roadblock, since the test times are so long. If this change only speeds up compiling

[jira] [Created] (KAFKA-18623) Enable ConsumerBounceTest testCloseDuringRebalance for new consumer

Lianet Magrans created KAFKA-18623: -- Summary: Enable ConsumerBounceTest testCloseDuringRebalance for new consumer Key: KAFKA-18623 URL: https://issues.apache.org/jira/browse/KAFKA-18623 Project: Kafk

[jira] [Created] (KAFKA-18622) Enable ConsumerBounceTest testClose for new consumer

Lianet Magrans created KAFKA-18622: -- Summary: Enable ConsumerBounceTest testClose for new consumer Key: KAFKA-18622 URL: https://issues.apache.org/jira/browse/KAFKA-18622 Project: Kafka Issu

[jira] [Resolved] (KAFKA-18575) Transaction Version 2 doesn't correctly handle race condition with completing and new transaction

[ https://issues.apache.org/jira/browse/KAFKA-18575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justine Olshan resolved KAFKA-18575. Resolution: Fixed > Transaction Version 2 doesn't correctly handle race condition with com

Jenkins build is still unstable: Kafka » Kafka PowerPC Daily » test-powerpc #187

See

Re: [DISCUSS] Changing which commit we build in PRs

It's a good question, Sophie. The answer is not entirely obvious. The build cache basically just loads the latest cache produced by the trunk builds. However, there are un-built commits on trunk quite frequently. These are commits which are being built by the current CI run, or are waiting for the

[jira] [Created] (KAFKA-18626) Support for windows that are more flexible to late arriving data

Almog Gavra created KAFKA-18626: --- Summary: Support for windows that are more flexible to late arriving data Key: KAFKA-18626 URL: https://issues.apache.org/jira/browse/KAFKA-18626 Project: Kafka

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #199

See Changes: -- Started by an SCM change Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on builds30 (ubuntu) in workspace

[DISCUSS] KIP-1124: Flexible Windows for Late Arriving Data

Hello! I'd like to initiate a discussion thread on KIP-1127: https://cwiki.apache.org/confluence/display/KAFKA/KIP-1127+Flexible+Windows+for+Late+Arriving+Data This KIP aims to make it easier to specify windowing semantics that are more tolerable to late arriving data, particularly with suppressi

[jira] [Created] (KAFKA-18628) Deprecate broker.id

Chia-Ping Tsai created KAFKA-18628: -- Summary: Deprecate broker.id Key: KAFKA-18628 URL: https://issues.apache.org/jira/browse/KAFKA-18628 Project: Kafka Issue Type: Improvement R

Re: [DISCUSS] Apache Kafka 4.0.0 release

hi David Could you please take a look at https://issues.apache.org/jira/browse/KAFKA-18627? This JIRA ticket introduces a new system environment variable and (possibly) deprecates the old one. Is it appropriate to include this change in 4.0? Thanks, Chia-Ping On 2025/01/20 11:55:24 David Jaco

[jira] [Created] (KAFKA-18627) Refactor JaasUtils

Chia-Ping Tsai created KAFKA-18627: -- Summary: Refactor JaasUtils Key: KAFKA-18627 URL: https://issues.apache.org/jira/browse/KAFKA-18627 Project: Kafka Issue Type: Improvement Re

Re: [DISCUSS] Apache Kafka 4.0.0 release

Hi David, +1 for adding KAFKA-18627 in v4.0.0. Besides, I'd also like to ask if we can include KAFKA-18230 into v4.0.0? The impact of KAFKA-18230

[jira] [Resolved] (KAFKA-18583) Improve/fix KRaftMetadataCache.getPartitionReplicaEndpoints

[ https://issues.apache.org/jira/browse/KAFKA-18583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-18583. - Resolution: Fixed > Improve/fix KRaftMetadataCache.getPartitionReplicaEndpoints > --

[jira] [Resolved] (KAFKA-18392) Require client-generated member IDs for ShareGroupHeartbeat

[ https://issues.apache.org/jira/browse/KAFKA-18392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-18392. -- Resolution: Fixed > Require client-generated member IDs for ShareGroupHeartbeat >