[jira] [Created] (KAFKA-16609) Update parse_describe_topic to support new topic describe output

Kirk True created KAFKA-16609: - Summary: Update parse_describe_topic to support new topic describe output Key: KAFKA-16609 URL: https://issues.apache.org/jira/browse/KAFKA-16609 Project: Kafka

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Thanks Alieh for the updates. I'm a little concerned about the design pattern here. It seems like we want specific usages, but we are packaging it as a generic handler. I think we tried to narrow down on the specific errors we want to handle, but it feels a little clunky as we have a generic

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Hi Alieh, Thanks for the KIP! A few questions: K1. What is the expected behavior for the producer if it generates a RecordTooLargeException, but the handler returns RETRY? K2. How do we determine which Record was responsible for the UnknownTopicOrPartitionException since we get that response

[PR] MINOR: Add Igor to committers [kafka-site]

soarez opened a new pull request, #598: URL: https://github.com/apache/kafka-site/pull/598  https://github.com/apache/kafka-site/assets/1357510/cccdd6e0-45d8-4e1a-949e-304d91815100;> -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [DISCUSS] KIP-1036: Extend RecordDeserializationException exception

Hi Fred, Thanks for the updates! Questions: K11. Can we reconsider the introduction of two new exception subclasses? Perhaps I don’t understand the benefit? Technically both the key and the value could have deserialization errors, right? K12. Is there a benefit to exposing both the

[jira] [Created] (KAFKA-16608) AsyncKafkaConsumer doesn't honour interrupted thread status on KafkaConsumer.poll(Duration)

Andrew Schofield created KAFKA-16608: Summary: AsyncKafkaConsumer doesn't honour interrupted thread status on KafkaConsumer.poll(Duration) Key: KAFKA-16608 URL:

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Alieh, Having run into issues with not being able to handle producer failures, I think this is good functionality to have. With this new functionality proposed at the Producer level, how would ecosystems that sit on top of it function? Specifically, Connect was updated a few years ago to allow

[jira] [Resolved] (KAFKA-16462) New consumer fails with timeout in security_test.py system test

[ https://issues.apache.org/jira/browse/KAFKA-16462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True resolved KAFKA-16462. --- Resolution: Duplicate > New consumer fails with timeout in security_test.py system test >

[jira] [Resolved] (KAFKA-16464) New consumer fails with timeout in replication_replica_failure_test.py system test

[ https://issues.apache.org/jira/browse/KAFKA-16464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirk True resolved KAFKA-16464. --- Resolution: Duplicate > New consumer fails with timeout in replication_replica_failure_test.py

Re: [DISCUSS] KIP-932: Queues for Kafka

Hi, Andrew, Thanks for the reply. 123. "it doesn’t need to confirm the assignment back to the GC." Hmm, I thought the member needs to confirm the assignment to GC to avoid GC including the assignment in the heartbeat response continuously. I assume this is done by including the new group epoch

[jira] [Created] (KAFKA-16607) Update the KIP and metrics implementation to include the new state

José Armando García Sancio created KAFKA-16607: -- Summary: Update the KIP and metrics implementation to include the new state Key: KAFKA-16607 URL: https://issues.apache.org/jira/browse/KAFKA-16607

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.7 #144

See

Re: [VOTE] KIP-853: KRaft Controller Membership Changes

Hi all, I am closing the voting. The KIP passed with: Jun Rao +1 binding Jason Gustafson +1 binding José Armando García Sancio +1 binding Thank you all, On Mon, Apr 22, 2024 at 11:57 AM José Armando García Sancio wrote: > > I am going to close the vote tomorrow morning (PST). > > On Mon, Apr

[jira] [Resolved] (KAFKA-16606) JBOD support in KRaft does not seem to be gated by the metadata version

[ https://issues.apache.org/jira/browse/KAFKA-16606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Scholz resolved KAFKA-16606. -- Resolution: Not A Problem > JBOD support in KRaft does not seem to be gated by the metadata

[jira] [Created] (KAFKA-16606) JBOD support in KRaft does not seem to be gated by the metadata version

Jakub Scholz created KAFKA-16606: Summary: JBOD support in KRaft does not seem to be gated by the metadata version Key: KAFKA-16606 URL: https://issues.apache.org/jira/browse/KAFKA-16606 Project:

[jira] [Created] (KAFKA-16605) Fix the flaky LogCleanerParameterizedIntegrationTest

Kamal Chandraprakash created KAFKA-16605: Summary: Fix the flaky LogCleanerParameterizedIntegrationTest Key: KAFKA-16605 URL: https://issues.apache.org/jira/browse/KAFKA-16605 Project: Kafka

[jira] [Created] (KAFKA-16604) Deprecate ConfigDef.ConfigKey constructor from public APIs

Sagar Rao created KAFKA-16604: - Summary: Deprecate ConfigDef.ConfigKey constructor from public APIs Key: KAFKA-16604 URL: https://issues.apache.org/jira/browse/KAFKA-16604 Project: Kafka Issue

Re: [DISCUSS] KIP-932: Queues for Kafka

Hi Jun, Thanks for the reply. 123. Every time the GC fails over, it needs to recompute the assignment for every member. However, the impact of re-assignment is not that onerous. If the recomputed assignments are the same, which they may well be, there is no impact on the members at all. On

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Thanks Matthias. I changed it to `custom.exception.handler` Alieh On Tue, Apr 23, 2024 at 8:47 AM Matthias J. Sax wrote: > Thanks Alieh! > > A few nits: > > > 1) The new config we add for the producer should be mentioned in the > "Public Interfaces" section. > > 2) Why do we use `producer.`

Re: [DISCUSS] KIP-1033: Add Kafka Streams exception handler for exceptions occuring during processing

Hi Matthias, Thanks for your reply! 100) That's a good point, I struggle to think of a case where it makes sense, but I am sure it exists. Let's keep this one for a future KIP as I think it would not be trivial to implement & tests. 101) As mentioned in KIP-1034, the error handler metadata

Re: [DISCUSS] KIP-1036: Extend RecordDeserializationException exception

Hi Andrew, A1. I will change the order of arguments to match. A2 and A3, Yes the KIP is not updated yet as I do not have a wiki account. So I must rely on some help to do those changes, which add some delay. I will try to find someone available ASAP. A4. I had the same thought. Using keyBuffer

Re: [DISCUSS] KIP-1036: Extend RecordDeserializationException exception

Hi Fred, Just reviewing the KIP again now that the discussion has quietened down a little. It will soon be ready for a vote I think. I have a few comments about details. A1) The signature of the new constructor for RecordDeserializationException needs to be updated accord to the discussion. I

Re: [DISCUSS] KIP-1038: Add Custom Error Handler to Producer

Thanks Alieh! A few nits: 1) The new config we add for the producer should be mentioned in the "Public Interfaces" section. 2) Why do we use `producer.` prefix for a *producer* config? Should it be `exception.handler` only? -Matthias On 4/22/24 7:38 AM, Alieh Saeedi wrote: Thank you

Re: [DISCUSS] KIP-1035: StateStore managed changelog offsets

Thanks for splitting out this KIP. The discussion shows, that it is a complex beast by itself, so worth to discuss by its own. Couple of question / comment: 100 `StateStore#commit()`: The JavaDoc says "must not be called by users" -- I would propose to put a guard in place for this, by