Jenkins build is unstable: Kafka » Kafka Branch Builder » trunk #2825

See

[jira] [Created] (KAFKA-16586) Test TaskAssignorConvergenceTest failing

Matthias J. Sax created KAFKA-16586: --- Summary: Test TaskAssignorConvergenceTest failing Key: KAFKA-16586 URL: https://issues.apache.org/jira/browse/KAFKA-16586 Project: Kafka Issue Type:

[jira] [Resolved] (KAFKA-16280) Expose method to determine Metric Measurability

[ https://issues.apache.org/jira/browse/KAFKA-16280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-16280. - Resolution: Done > Expose method to determine Metric Measurability >

Build failed in Jenkins: Kafka » Kafka Branch Builder » trunk #2824

See Changes: -- [...truncated 369635 lines...] [2024-04-19T00:09:45.150Z] [2024-04-19T00:09:45.150Z] Gradle Test Run :streams:test > Gradle Test Executor 30 >

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

Thanks for all the context everyone. I think in light of all the information that's been shared, I would agree with David that neither the Record nor ConsumerRecord feels appropriate and that we should just create a new class/interface that holds the info we want to expose. We definitely don't

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

Thanks for the KIP Alieh! It addresses an important case for error handling. I agree that using this handler would be an expert API, as mentioned by a few people. But I don't think it would be a reason to not add it. It's always a tricky tradeoff what to expose to users and to avoid foot guns,

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

Hi Fred, thanks for the KIP. Seems like a useful improvement. As others have mentioned, I think we should avoid exposing Record in this way. Using ConsumerRecord seems okay, but maybe not the best fit for this case (for the reasons Matthias gave). Maybe we could create a new container interface

[jira] [Resolved] (KAFKA-16389) consumer_test.py’s test_valid_assignment fails with new consumer

[ https://issues.apache.org/jira/browse/KAFKA-16389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Philip Nee resolved KAFKA-16389. Resolution: Fixed > consumer_test.py’s test_valid_assignment fails with new consumer >

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

Andrew, thanks for the details about Consumer internals. That's super useful for this discussion! -- And it confirms my understanding. I don't think we want to use ConsumerRecord type thought, because for a DLQ the handler wants to write the message into some DLQ topic, and thus needs the key

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

Hi Alieh, Thanks for the KIP. Exception handling in the Kafka producer and consumer is really not ideal. It’s even harder working out what’s going on with the consumer. I’m a bit nervous about this KIP and I agree with Chris that it could do with additional motivation. This would be an

Re: [ANNOUNCE] New Kafka PMC Member: Greg Harris

Congratulations Greg! On Thu, Apr 18, 2024 at 12:03 AM Matthias J. Sax wrote: > Congrats Greg! > > On 4/15/24 10:44 AM, Hector Geraldino (BLOOMBERG/ 919 3RD A) wrote: > > Congrats! Well deserved > > > > From: dev@kafka.apache.org At: 04/13/24 14:42:22 UTC-4:00To: > dev@kafka.apache.org > >

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

Hi, Thanks for the KIP. I think it’s an interesting idea and it seems to work nicely with how the clients work today. Recently, I’ve been digging in to the record deserialization code in the consumer as part of implementing KIP-932. It’s pretty nasty in there. There are essentially two kinds

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

Hi, But I guess my main question is really about what metadata we really > want to add to `RecordDeserializationException`? `Record` expose all > kind of internal (serialization) metadata like `keySize()`, > `valueSize()` and many more. For the DLQ use-case it seems we don't > really want any of

[jira] [Created] (KAFKA-16585) No way to forward message from punctuation method in the FixedKeyProcessor

Stanislav Spiridonov created KAFKA-16585: Summary: No way to forward message from punctuation method in the FixedKeyProcessor Key: KAFKA-16585 URL: https://issues.apache.org/jira/browse/KAFKA-16585

Re: [DISCUSS] KIP-924: customizable task assignment for Streams

Hi Sophie, Thanks for the clarifications! (1) What about replacing Node* with KafkaStreams* or StreamsClient*? I prefer KafkaStreams* since that class represents the Kafka Streams client. I am also fine with KafkaStreamsClient*. I really would like to avoid introducing a new term in Kafka

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

Hi, I am actually not sure if using `Record` is really the right thing? While `Record` is technically public API, it does not seem to be intended to be exposed to end users? But I guess my main question is really about what metadata we really want to add to `RecordDeserializationException`?

[jira] [Created] (KAFKA-16584) Make log processing summary configurable or debug

Andras Hatvani created KAFKA-16584: -- Summary: Make log processing summary configurable or debug Key: KAFKA-16584 URL: https://issues.apache.org/jira/browse/KAFKA-16584 Project: Kafka Issue

Re: [ANNOUNCE] New Kafka PMC Member: Greg Harris

Congrats Greg! On 4/15/24 10:44 AM, Hector Geraldino (BLOOMBERG/ 919 3RD A) wrote: Congrats! Well deserved From: dev@kafka.apache.org At: 04/13/24 14:42:22 UTC-4:00To: dev@kafka.apache.org Subject: [ANNOUNCE] New Kafka PMC Member: Greg Harris Hi all, Greg Harris has been a Kafka committer

[jira] [Created] (KAFKA-16583) Update from 3.4.0 to 3.7.0 image write failed in Kraft mode

HanXu created KAFKA-16583: - Summary: Update from 3.4.0 to 3.7.0 image write failed in Kraft mode Key: KAFKA-16583 URL: https://issues.apache.org/jira/browse/KAFKA-16583 Project: Kafka Issue Type: