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

Hi, Jiunn-Yang, Thanks for the reply. If we omit the non-existing value in the return map, for applications that care about the missing value, is it convenient for them to write the code? They need to save the input to find this out, right? Jun On Fri, May 9, 2025 at 4:39 AM 黃竣陽 wrote: > Hi

Re: [DISCUSS] KIP-1176: Tiered Storage for Active Log Segment

Yes Stan, That issue (modify FetchRequest/Response API to carry the extra metadata for the active log segment in object storage) was discussed with Luke, in case that apache email thread is difficult to read, here is what I said earlier: HC>. I like your idea of using FetchResponse to carry the

[jira] [Resolved] (KAFKA-19116) Deletion of share group offsets does not reset the position as expected

[ https://issues.apache.org/jira/browse/KAFKA-19116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19116. --- Resolution: Fixed > Deletion of share group offsets does not reset the position as expected

Re: KIP-1182 Quality of Service (QoS) for Apache Kafka

Hi Peter and David, Thanks for the KIP. It contains some interesting ideas but it's very nebulous at this point. I think the suggestion of a proxy layer in front of Kafka is a good way to start probing at this. Are the existing Kafka metrics helpful for QoS? What changes might we make to the Kaf

[jira] [Created] (KAFKA-19279) DefaultMessageFormatter is inaccessible as it's package-private class

Aniruddha Navare created KAFKA-19279: Summary: DefaultMessageFormatter is inaccessible as it's package-private class Key: KAFKA-19279 URL: https://issues.apache.org/jira/browse/KAFKA-19279 Project

[jira] [Resolved] (KAFKA-19258) Release acquired records for members whose share session is evicted due to connection drop

[ https://issues.apache.org/jira/browse/KAFKA-19258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19258. --- Fix Version/s: 4.1.0 Resolution: Fixed > Release acquired records for members whose s

[jira] [Created] (KAFKA-19283) Update Apache kafka public documentation

Kaushik Raina created KAFKA-19283: - Summary: Update Apache kafka public documentation Key: KAFKA-19283 URL: https://issues.apache.org/jira/browse/KAFKA-19283 Project: Kafka Issue Type: Sub-ta

[jira] [Resolved] (KAFKA-19273) Ensure the delete policy is configured when the tiered storage is enabled

[ https://issues.apache.org/jira/browse/KAFKA-19273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19273. Fix Version/s: 4.1.0 Resolution: Fixed > Ensure the delete policy is configured whe

[jira] [Created] (KAFKA-19282) Update quotaTypesEnabled on quota removal in ClientQuotaManager

Mahsa Seifikar created KAFKA-19282: -- Summary: Update quotaTypesEnabled on quota removal in ClientQuotaManager Key: KAFKA-19282 URL: https://issues.apache.org/jira/browse/KAFKA-19282 Project: Kafka

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

+1 non binding Thanks On Sat, Apr 26, 2025 at 4:32 PM Kirk True wrote: > > +1 (non-binding) > > Thanks! > > On Sat, Apr 26, 2025, at 3:14 AM, PoAn Yang wrote: > > +1 (non-binding) > > > > Thanks, > > PoAn > > > > > On Apr 26, 2025, at 4:10 PM, Chia-Ping Tsai wrote: > > > > > > +1 (binding) > >

[jira] [Resolved] (KAFKA-19234) broker should return UNAUTHORIZATION error for non-existing topic in produce request

[ https://issues.apache.org/jira/browse/KAFKA-19234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jun Rao resolved KAFKA-19234. - Fix Version/s: 4.1.0 Resolution: Fixed merged the PR to trunk > broker should return UNAUTHORIZA

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

Thanks Ivan for the KIP, +1 (binding) ~Satish. On Wed, 14 May 2025 at 16:09, Christo Lolov wrote: > > Hello! > > Apologies for coming late to the party. I think this is a great idea and > don't see why we can't try it out in practice! > > +1 (binding) > > Best, > Christo > > On Tue, 29 Apr 2025

Re: [VOTE] KIP-1135: Deprecated "org.apache.kafka.disallowed.login.modules"

Hi Chia-Ping You are right. I don't think this should be optional. We should enforce the use of the allowlist Chia-Ping Tsai 于2025年5月14日周三 13:07写道： > hi Xuan-Zhang > > (optional) we can deprecate `org.apache.kafka.disallowed.login.modules` and > print warning message when users explicitly define

[jira] [Created] (KAFKA-19280) NoSuchElementException in UnifiedLog.fetchLastStableOffsetMetadata

Lucas Brutschy created KAFKA-19280: -- Summary: NoSuchElementException in UnifiedLog.fetchLastStableOffsetMetadata Key: KAFKA-19280 URL: https://issues.apache.org/jira/browse/KAFKA-19280 Project: Kafka

Re: [DISCUSS] KIP-1176: Tiered Storage for Active Log Segment

Hi Stanislav, I already gave a similar suggestion to Henry earlier, and you can see his response here: https://lists.apache.org/thread/v8t7co0517hw2tlm0ypn8tnjfmhnhv83 . Good to see you have the same thought. :) Thanks. Luke On Wed, May 14, 2025 at 6:31 PM Stanislav Kozlovski < stanislavkozlov.

Re: [DISCUSS] KIP-1183: Unified Shared Storage

Hi Luke, Thank you for your review and insightful questions. 1. Regarding the future plan for this KIP, once we establish an abstract log layer, we might implement a default version on object storage for Kafka. For other types of shared storage, we'll decide based on community needs. 2. In my vi

Re: [DISCUSS] KIP-1183: Unified Shared Storage

Hi Satish, Thanks for your incisive comments! For SD-1: I am now confident that we have a better chance of reaching a consensus on the abstract layer. I will complete this part and address all the questions from you and Luke. Once finished, I will ping you again. For SD-2: In this KIP, a partiti

Re: [VOTE] 3.9.1 RC2

Hi all, Thanks for the vote so far! Update for the system test: 1. The system tests have some failed tests: http://jenkins.opensource4you.tw/job/kafka-e2e/317 2. The failed benchmark_test and OffsetValidationTest can pass in another run: https://drive.google.com/drive/folders/1lf7EH-m8PNPGfv7Fj3-

[jira] [Resolved] (KAFKA-19143) Setup periodic job to clean share group deleting metadata state in GC

[ https://issues.apache.org/jira/browse/KAFKA-19143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sushant Mahajan resolved KAFKA-19143. - Resolution: Not A Problem > Setup periodic job to clean share group deleting metadata st

[jira] [Created] (KAFKA-19281) Add metadata version check to enable share coordinator timer tasks.

Sushant Mahajan created KAFKA-19281: --- Summary: Add metadata version check to enable share coordinator timer tasks. Key: KAFKA-19281 URL: https://issues.apache.org/jira/browse/KAFKA-19281 Project: Ka

Re: [DISCUSS] KIP-1183: Unified Shared Storage

Hi Xinyu, Thanks for the proposal! I agree abstracting the log and logSegment layers can allow users to implement any kinds of storage mediums. Some high-level comments: 1. I expect to see the future plan of this KIP, but can't find it. What do you expect to achieve the "shared storage" goal afte

Re: [DISCUSS] KIP-1176: Tiered Storage for Active Log Segment

Have we considered using the traditional replication path to store the actual metadata for the topic/partition? I know the KIP says "The main purpose of FollowerFetchRequest/FollowerFetchResponse is now just to update the offsets and high watermark between leader and follower.", but what if we

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

Hello! Apologies for coming late to the party. I think this is a great idea and don't see why we can't try it out in practice! +1 (binding) Best, Christo On Tue, 29 Apr 2025 at 15:16, Andrew Schofield < andrew_schofield_j...@outlook.com> wrote: > Thanks for the KIP, Ivan. > > +1 (binding) > >

Re: [DISCUSS] KIP-1183: Unified Shared Storage

Thanks Xinyu for accepting our request to initiate a KIP on AutoMq's proposal. SD-1: It is a good start towards building log storage layer abstractions, including LogSegment and Log, for both local and shared storage. However, more clarity is needed on how these abstractions are defined. The class

Re: [DISCUSS] Apache Kafka 4.1.0 release

Hi, Reminder that today is KIP freeze. If you have a KIP that has been approved before the end of the day, you can add it to the 4.1.0 release plan. The next milestone is feature freeze on June 4. Thanks, Mickael On Tue, May 13, 2025 at 6:48 PM Mickael Maison wrote: > > Hi Kirk, > Yes it was a

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

See

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

+1 binding from me. Thanks. Luke On Wed, May 14, 2025 at 7:14 PM Satish Duggana wrote: > Thanks Ivan for the KIP, +1 (binding) > > ~Satish. > > On Wed, 14 May 2025 at 16:09, Christo Lolov > wrote: > > > > Hello! > > > > Apologies for coming late to the party. I think this is a great idea and >

[jira] [Resolved] (KAFKA-19270) Remove optional from ClusterInstance#controllerListenerName

[ https://issues.apache.org/jira/browse/KAFKA-19270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] TengYao Chi resolved KAFKA-19270. - Resolution: Fixed > Remove optional from ClusterInstance#controllerListenerName > --