[jira] [Resolved] (KAFKA-19267) the min version used by ListOffsetsRequest should be 1 rather than 0

[ https://issues.apache.org/jira/browse/KAFKA-19267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19267. Fix Version/s: 4.1.0 Resolution: Fixed > the min version used by ListOffsetsRequest

Re: Request to permission

hi Jiseung I have added you to the contributor group. Additionally, I have assigned the issue to you welcome to Kafka community :) Best, chia-ping Ji-Seung Ryu <8514...@gmail.com> 於 2025年5月16日 週五 上午10:22寫道： > Hi, > > My JIRA username is: jiseung > > Currently, I am not able to be assigned JIRA

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

hi Jun > For 1, is it better to skip the missing value in the return map or include it? To me, including every item passed in from the input seems more intuitive and less error prone for the users. Yes, I agree that using null for now is suitable. Especially considering the growing number of offs

Request to permission

Hi, My JIRA username is: jiseung Currently, I am not able to be assigned JIRA tickets. Can you give me permission to do it? https://issues.apache.org/jira/browse/KAFKA-19268 Thank you. Best regards, Jiseung Ryu

[jira] [Resolved] (KAFKA-19289) Read only disk failure, ReplicaManager.scala's logManager.handleLogDirFailure(dir) not capturing exception correctly, interrupt process causing topic with multiple cop

[ https://issues.apache.org/jira/browse/KAFKA-19289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] felixzh resolved KAFKA-19289. - Resolution: Fixed > Read only disk failure, ReplicaManager.scala's > logManager.handleLogDirFailure(dir

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

Hi Colin, Thank you for taking the time to read this KIP, and no worries, negative feedback is a catalyst for improvement. Sorry for the inappropriate description in the Motivation section; my background influenced my writing, but I didn’t mean it. I will remove it. Thanks for the reminder. I co

[jira] [Created] (KAFKA-19289) Read only disk failure, ReplicaManager.scala's logManager.handleLogDirFailure(dir) not capturing exception correctly, interrupt process causing topic with multiple copi

felixzh created KAFKA-19289: --- Summary: Read only disk failure, ReplicaManager.scala's logManager.handleLogDirFailure(dir) not capturing exception correctly, interrupt process causing topic with multiple copies partition leader failure not switching.

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

Hi Xinyu Zhou, Thanks for the KIP. It's good to see more people contributing to the community. I think this is your first KIP, so please forgive me for giving some negative feedback. KIPs need to be written in a vendor-neutral manner, for the whole community. So please do not do things like be

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hi Kevin, On Thu, May 15, 2025 at 10:52 AM Kevin Wu wrote: > Thanks for all the comments about the metric type field for the minimum and > maximum supported feature levels. I agree they are software version > specific. Also, since they are shared across the broker and controller like > the Finali

[jira] [Created] (KAFKA-19288) Ensure new consumer joining attempt not overwritten on delayed HB response to previous leave

Lianet Magrans created KAFKA-19288: -- Summary: Ensure new consumer joining attempt not overwritten on delayed HB response to previous leave Key: KAFKA-19288 URL: https://issues.apache.org/jira/browse/KAFKA-19288

[jira] [Created] (KAFKA-19287) docuemnt all group coordinator metrics

Chia-Ping Tsai created KAFKA-19287: -- Summary: docuemnt all group coordinator metrics Key: KAFKA-19287 URL: https://issues.apache.org/jira/browse/KAFKA-19287 Project: Kafka Issue Type: Improv

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

Hi, Chia-Ping, Yes, there are two things to consider. 1. What's the desired way for returning a map when some of the values are not present? 2. Once we agreed on a desired way, how to make that consistent across all APIs. For 1, is it better to skip the missing value in the return map or includ

Re: [DISCUSS] KIP-1174: Expose addReadOnlyStateStore in DSL (StreamsBuilder)

Hello Kafka Community, Please review this KIP. Thank you. Best regards, Siddhartha Devineni On Fri, May 2, 2025 at 4:15 PM Siddhartha Devineni < siddhartha.devin...@gmail.com> wrote: > Hello all, > > Here is the link to the PR that is implemented according to the KIP, > please review it for any

Re: [VOTE] 3.9.1 RC2

Hey folks, Thanks for the updated RC, I'm happy to see the correct version now in documentation :) I built from source, ran a kraft and zk cluster and a basic trogdor workload for each. I took a quick look at the diff to see the changes compared to the last RC I validated. I also took a quick loo

[jira] [Resolved] (KAFKA-19274) Group Coordinator Shards are not unloaded when __consumer_offsets topic is deleted

[ https://issues.apache.org/jira/browse/KAFKA-19274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-19274. - Fix Version/s: 4.0.1 4.1.0 Resolution: Fixed > Group Coordinator Shard

[jira] [Created] (KAFKA-19286) RemoteIndexCacheTest.testConcurrentRemoveReadForCache1 is flaky

Andrew Schofield created KAFKA-19286: Summary: RemoteIndexCacheTest.testConcurrentRemoveReadForCache1 is flaky Key: KAFKA-19286 URL: https://issues.apache.org/jira/browse/KAFKA-19286 Project: Kafk

[jira] [Resolved] (KAFKA-19206) ConsumerNetworkThread.cleanup() throws NullPointerException if initializeResources() previously failed

[ https://issues.apache.org/jira/browse/KAFKA-19206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True resolved KAFKA-19206. --- Resolution: Fixed > ConsumerNetworkThread.cleanup() throws NullPointerException if > initializeReso

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hi all, Thanks for all the comments about the metric type field for the minimum and maximum supported feature levels. I agree they are software version specific. Also, since they are shared across the broker and controller like the FinalizedLevel metric, having two separate metrics is redundant an

[jira] [Resolved] (KAFKA-19253) Improve metadata handling for share version using feature listeners

[ https://issues.apache.org/jira/browse/KAFKA-19253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19253. --- Fix Version/s: 4.1.0 Resolution: Fixed > Improve metadata handling for share version

[jira] [Resolved] (KAFKA-19231) Handle fetch request when share session cache is full

[ https://issues.apache.org/jira/browse/KAFKA-19231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19231. --- Fix Version/s: 4.1.0 Resolution: Fixed > Handle fetch request when share session cach

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

[ https://issues.apache.org/jira/browse/KAFKA-19281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Apoorv Mittal resolved KAFKA-19281. --- Fix Version/s: 4.1.0 Resolution: Fixed > Add metadata version check to enable share c

[jira] [Resolved] (KAFKA-19263) The docs of delete.topic.enable used by Admin#deletetopics is out-of-date

[ https://issues.apache.org/jira/browse/KAFKA-19263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19263. Fix Version/s: 4.1.0 Resolution: Fixed > The docs of delete.topic.enable used by Ad

Re: [VOTE] 3.9.1 RC2

Hi, I’ve completed the following tasks: - Verified the signatures and checksums of all release artifacts - Built from source (23.0.2-oracle + Scala 2.13) - Ran unit tests & integration tests - Ran the Kafka quickstart & Kafka Streams quickstart with the downloaded binary - Ran the Kafka quickstar

Re: [DISCUSS] KIP-1178: Introduce remote.max.partition.fetch.bytes in Consumer

Hi Andrew, in general it's an expected case that the broker returns more data than the limits, as it returns at least one MessageSet. All messages that can be parsed are enqueued. If there's a buffer underflow because of the truncation by the broker the parsing stops at last complete message. If th

[jira] [Created] (KAFKA-19285) Imrove test coverage for SharePartitionManager

Apoorv Mittal created KAFKA-19285: - Summary: Imrove test coverage for SharePartitionManager Key: KAFKA-19285 URL: https://issues.apache.org/jira/browse/KAFKA-19285 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-1150 Diskless Topics

looks like it will write data to remote OSS directly, I'm just wandering that do we need to make storage API async? Kafka's storage API is fully sync, in this case, if we write data to s3 directly and wait the response, I'm afraid the throughput can be very low. But if we make it async, it will

Re: [DISCUSS] KIP-1180: Add a generic feature level metric

Hi Kevin, Thanks for the KIP. 4. How about using a new metric type to collect all feature metrics? So we don’t need to have different metric names in controller and broker. For example: * kafka.server:type=FeatureMetrics,name=FinalizedLevel,featureName=X * kafka.server:type=FeatureMetrics,name=Mi

Re: [VOTE] KIP-1175: Fix the typo `PARTITIONER_ADPATIVE_PARTITIONING_ENABLE` in ProducerConfig

Hi Chia-Ping That’s right — in fact, I’ve already marked the DOC variable with // Remove in the KIP to indicate that it’s meant to be removed. I’ll also add a comment at the ConfigDef().define location to clarify that the typo’d DOC variable is intended to be removed entirely. Best, Ming-Yen Chi

Re: [VOTE] KIP-1175: Fix the typo `PARTITIONER_ADPATIVE_PARTITIONING_ENABLE` in ProducerConfig

hi Ming-Yen Could you please eliminate the duplicate code? For example, the deprecated docs can reference to new docs, right? Best, Chia-Ping Ming-Yen Chung 於 2025年5月15日 週四 下午4:11寫道： > Hi all, I would like to start the voting process for KIP-1175: Fix the > typo `PARTITIONER_ADPATIVE_PARTITIO

[VOTE] KIP-1175: Fix the typo `PARTITIONER_ADPATIVE_PARTITIONING_ENABLE` in ProducerConfig

Hi all, I would like to start the voting process for KIP-1175: Fix the typo `PARTITIONER_ADPATIVE_PARTITIONING_ENABLE` in ProducerConfig Discussion thread: https://lists.apache.org/thread/zsxzovgh2skxysmjx54z34294hhjfhhl Thanks, Ming-Yen

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

hi Jun I understand the use case where the "Result" is expected to represent both "exist" and "non-exist." However, I'm concerned about consistency across our APIs. Not all of Admin APIs follow this pattern; for example, listPartitionReassignments and describeProducers do not. Designing a single A

[jira] [Created] (KAFKA-19284) add documentation to clarify the behavior of null values for all partitionsToOffsetAndMetadata methods.

Chia-Ping Tsai created KAFKA-19284: -- Summary: add documentation to clarify the behavior of null values for all partitionsToOffsetAndMetadata methods. Key: KAFKA-19284 URL: https://issues.apache.org/jira/browse/KA

[jira] [Resolved] (KAFKA-19269) "Unexpected error .." should not happen when the delete.topic.enable is false

[ https://issues.apache.org/jira/browse/KAFKA-19269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-19269. Fix Version/s: 4.1.0 Resolution: Fixed > "Unexpected error .." should not happen wh