[jira] [Created] (KAFKA-19215) Handle share partition fetch lock cleanly in DelayedShareFetch to avoid a member incorrectly releasing a share partition's fetch lock

Abhinav Dixit created KAFKA-19215: - Summary: Handle share partition fetch lock cleanly in DelayedShareFetch to avoid a member incorrectly releasing a share partition's fetch lock Key: KAFKA-19215 URL: https://iss

[jira] [Resolved] (KAFKA-18288) Add support kafka-streams-groups.sh --describe

[ https://issues.apache.org/jira/browse/KAFKA-18288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alieh Saeedi resolved KAFKA-18288. -- Resolution: Fixed > Add support kafka-streams-groups.sh --describe > -

[jira] [Resolved] (KAFKA-19173) Add `Feature` for streams groups

[ https://issues.apache.org/jira/browse/KAFKA-19173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-19173. - Fix Version/s: 4.1.0 Resolution: Fixed > Add `Feature` for streams groups > -

[jira] [Resolved] (KAFKA-16758) Extend Consumer#close with option to leave the group or not

[ https://issues.apache.org/jira/browse/KAFKA-16758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-16758. - Resolution: Fixed > Extend Consumer#close with option to leave the group or not > --

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

See

Re: [PR] KAFKA-19209: Clarify index.interval.bytes impact on offset and time index [kafka-site]

shmily7829 commented on code in PR #686: URL: https://github.com/apache/kafka-site/pull/686#discussion_r2067643570 ## 40/generated/topic_config.html: ## @@ -111,7 +111,12 @@ index.interval.bytes -This setting controls how frequently Kafka adds an index entry to its offset index

[jira] [Resolved] (KAFKA-19135) Add IQ Support - move from feature branch

[ https://issues.apache.org/jira/browse/KAFKA-19135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Bejeck resolved KAFKA-19135. - Resolution: Fixed > Add IQ Support - move from feature branch >

Re: [DISCUSS] KIP-1140: Avoid to return null value in Map from public api of consumer

Hi, Jiunn-Yang, Thanks for the KIP. It would be useful to think through the consistency with adminClient.listOffset(). Currently, if the offset for a timestamp doesn't exist, consumer.offsetsForTimes() returns a null value for that partition while adminClient.listOffset().all().get() returns a Li

[jira] [Created] (KAFKA-19214) Clean up use of Optionals in RequestManagers.entries()

Kirk True created KAFKA-19214: - Summary: Clean up use of Optionals in RequestManagers.entries() Key: KAFKA-19214 URL: https://issues.apache.org/jira/browse/KAFKA-19214 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-1119: Add support for SSL hot reload

Gaurav brings up a good point. However, we can work around that bug by doing polling every 5 or 10 minutes in addition to using WatchService. best, Colin On Wed, Apr 23, 2025, at 00:39, Gaurav Narula wrote: > Hi Moncef, > > Have you tried experimenting the behaviour of JDK's WatchService with >

Re: [DISCUSS] KIP-1139: Add support for OAuth jwt-bearer grant type

Hi all! I've published an update KIP, which includes: 1. Clarity and corrections for all of the feedback 2. Use of the mock-oauth2-server library for integration testing 3. Reduced the public exposure of some of the internals (assertion creation, file caching, etc.) I'd like to call a vote soon

Re: [DISCUSS] KIP-1166: Improve high-watermark replication

Hi José, Wondering if there is perhaps a typo - under *KRaft Handling *the wording mentions parking the request if the HWM in the request is >= to the leader's > If the response is empty and the remote replica's HWM is greater than or > equal to the leader's HWM, the FETCH request is parked. Und

Re: [PR] KAFKA-19209: Clarify index.interval.bytes impact on offset and time index [kafka-site]

brandboat commented on code in PR #686: URL: https://github.com/apache/kafka-site/pull/686#discussion_r2067026790 ## 40/generated/topic_config.html: ## @@ -111,7 +111,12 @@ index.interval.bytes -This setting controls how frequently Kafka adds an index entry to its offset index.

[PR] KAFKA-19209: Clarify index.interval.bytes impact on offset and time index [kafka-site]

shmily7829 opened a new pull request, #686: URL: https://github.com/apache/kafka-site/pull/686 Update docs to note index.interval.bytes sets entry frequency for offset index and, conditionally, time index. -- This is an automated message from the Apache Git Service. To respond to the mess

Re: [VOTE] KIP-1142: Allow to list non-existent group which has dynamic config

Hi all, Thanks for your voting and participation. The KIP-1142 has been accepted with 3 binding +1 from Andrew Schofield, TengYao Chi, and Chia-Ping Tsai. Thanks for everyone. Regards, PoAn > On Apr 23, 2025, at 8:06 PM, Chia-Ping Tsai wrote: > > +1 (binding) > > Thanks, > Chia-Ping > > Te

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

Hi Chia-Ping, chia_00: I'll update the KIP, thanks! chia_01: Regarding "partition(TopicPartition topicPartition)", it should return an Optional. For the others, we should either return an empty map (e.g., partitionsForTopic(String topic)) or an empty list (e.g., offlineReplicas(PartitionMetada

[jira] [Created] (KAFKA-19213) Kafka java client ignores default properties

Pas Filip created KAFKA-19213: - Summary: Kafka java client ignores default properties Key: KAFKA-19213 URL: https://issues.apache.org/jira/browse/KAFKA-19213 Project: Kafka Issue Type: Bug

Re: [VOTE] KIP-1123: Rack-aware partitioning for Kafka Producer

Thanks for the KIP, Ivan. +1 (binding) Thanks, Andrew From: Josep Prat Sent: 29 April 2025 11:57 To: dev@kafka.apache.org Subject: Re: [VOTE] KIP-1123: Rack-aware partitioning for Kafka Producer Thanks for the KIP Ivan! +1 binding Best, On Tue, Apr 22

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

hi Kuan-Po Thanks for updating KIP. This approach is better. Some comments are listed below. chia_00: Could you please update docs of `ClientQuotaCallback` to remind users to use ClientQuotaCallbackHandler instead. chia_01: what happens if users query a non-existent object? throw exception? o

Re: [VOTE] KIP-1123: Rack-aware partitioning for Kafka Producer

Thanks for the KIP Ivan! +1 binding Best, On Tue, Apr 22, 2025 at 8:56 PM Hector Geraldino (BLOOMBERG/ 919 3RD A) < hgerald...@bloomberg.net> wrote: > +1 non-binding > > From: dev@kafka.apache.org At: 03/31/25 09:08:17 UTC-4:00To: > dev@kafka.apache.org > Subject: Re: [VOTE] KIP-1123: Rack-aware

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

Hi Colin, I was thinking about it some more, and I feel like it might be better to have the old interface extend the new one. That way, it’ll be easier for us to remove the old interface later — we wouldn’t have to change too much code, just delete the old one. It would still keep everything

Re: [DISCUSS] KIP-1043: Administration of groups

Hi Chia-Ping, I think that's an excellent idea. I prefer to write a new KIP at this point, since KIP-1043 will be complete when the last PR currently under review merges. I anticipate adding a handful of enhancements: * Protocol filter for groups * Pattern filter * Optional group type on group del

Re: [VOTE] KIP-1131: Improved controller-side monitoring of broker states

Hi Kevin Thanks for this great KIP! +1 (binding) Best, TengYao Chia-Ping Tsai 於 2025年4月29日 週二 下午4:15寫道： > hi Kevin > > PoAn is not yet a Kafka committer. I hope he can make more contributions > to get promoted. > > Regarding the KIP, it looks good to me. +1 (binding) > > One small question: >

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

Hi everyone, Colin: You’re right. I’ll adjust the KIP as you suggested—creating a new interface that extends the old one to avoid any compilation issues when we eventually remove the old method. However, Chia-Ping also suggested another approach: creating a completely new interface that has no

Re: [DISCUSS] KIP-1162: Redesign ClientQuotaCallback#updateClusterMetadata

hi Kuan-Po Could you please add the approaches we discussed before to "rejected" section? It could help readers to understand the picture easily. Best, Chia-Ping On 2025/04/29 04:32:52 Chia-Ping Tsai wrote: > hi Colin > > the interface `ClientQuotaCallackHandler` is a typo - the idea of this P

Re: [VOTE] KIP-1131: Improved controller-side monitoring of broker states

hi Kevin PoAn is not yet a Kafka committer. I hope he can make more contributions to get promoted. Regarding the KIP, it looks good to me. +1 (binding) One small question: Why use "number" instead of "string" to represent the state? There are other state-related metrics, such as "current-stat

Re: [DISCUSS] - KIP-1064: Upgrade slf4j to 2.x

hi Colin The compatibility issue could arise if the version of the custom SLF4j provider used by users does not match the SLF4j API version bundled with Kafka. For example, if we upgrade the SLF4j API version to 2.x, users who are still using slf4j-simple 1.x might encounter some issues. See the S