[jira] [Resolved] (KAFKA-13398) The caller program will be shut down directly when the execution of Kafka script is abnormal

[ https://issues.apache.org/jira/browse/KAFKA-13398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RivenSun resolved KAFKA-13398. -- Resolution: Not A Problem > The caller program will be shut down directly when the execution of Kafka

Re: [DISCUSS] KIP-831: Add metric for log recovery progress

The KIP describes RemainingLogsToRecovery, which seems to be the number of partitions in each log.dir. We have some partitions which are much much larger than others. Those large partitions have many many more segments than others. Is there a way the metric can reflect partition size? Could

Re: [DISCUSS] KIP-759: Unneeded repartition canceling

Ivan, are you still interested in this KIP? I think it would be a good addition. -Matthias On 8/16/21 5:30 PM, Matthias J. Sax wrote: Your point about the IQ problem is an interesting one. I missed the point that the "new key" would be a "superkey", and thus, it should always be possible to

Re: [DISCUSS] KIP-819: Merge multiple KStreams in one operation

Nick, how should we proceed? On 3/29/22 9:21 PM, Chris Egerton wrote: Hi all, The Named-first variant seems pretty appealing: merge(Named named, KStream... streams) It doesn't align with the existing merge methods, but it does at least follow precedent set by the (now-deprecated) branch

Jenkins build is still unstable: Kafka » Kafka Branch Builder » trunk #884

See

Re: contributor access

Just added you. Thanks for your interest to contribute to the Apache Kafka project Andras! Konstantine On Fri, Apr 22, 2022 at 7:25 AM András Csáki wrote: > Hi Kafka Devs, > > I'd like to start contributing to Apache Kafka, first with a fix for > KAFKA-13848

[jira] [Created] (KAFKA-13851) Tests are missing for DeleteRecords API

Divij Vaidya created KAFKA-13851: Summary: Tests are missing for DeleteRecords API Key: KAFKA-13851 URL: https://issues.apache.org/jira/browse/KAFKA-13851 Project: Kafka Issue Type:

Re: [DISCUSS] KIP-830: Allow disabling JMX Reporter

Hi Mickael, what about setting the default value to JmxReporter while also maintaining the old behavior? When a user is setting metric.reporters without explicitly including the JmxReporter, we could simply print a warning message which says "The automatic addition of the JmxReporter is

Build failed in Jenkins: Kafka » kafka-2.7-jdk8 #189

See Changes: -- [...truncated 6.93 MB...] org.apache.kafka.streams.test.OutputVerifierTest >

contributor access

Hi Kafka Devs, I'd like to start contributing to Apache Kafka, first with a fix for KAFKA-13848 I've just reported. Please add me to the list of contributors so I can assign this task to myself and submit a PR! :) My jira ID is: acsaki Thank

Re: [DISCUSS] KIP-829: (console-consumer) add print.topic property

Hi, everyone, Thanks for the comment on writing the example on KIP. I'm glad this KIP is well received. There's this other message queue called `nsq` with the consumer program `nsq_tail` and it has the ability to print the topic, which is useful when consuming from wildcard (includes), which led

[jira] [Created] (KAFKA-13850) kafka-metadata-shell is missing some record types

David Arthur created KAFKA-13850: Summary: kafka-metadata-shell is missing some record types Key: KAFKA-13850 URL: https://issues.apache.org/jira/browse/KAFKA-13850 Project: Kafka Issue

[jira] [Resolved] (KAFKA-13849) All topics whose cleanup policy contains `compact` are not executing deleteLogStartOffsetBreachedSegments as expected

[ https://issues.apache.org/jira/browse/KAFKA-13849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] RivenSun resolved KAFKA-13849. -- Resolution: Not A Bug > All topics whose cleanup policy contains `compact` are not executing >

Re: [DISCUSS] KIP-821: Connect Transforms support for nested structures

Hello all! Sorry that I come a bit later to the party here, but I am the one who wrote KIP-683 [1] for recursive support (just simply looping through all child non-primitive structures for the same matching name(s)) which is a slightly different way to try and solve a similar requirement --

[jira] [Created] (KAFKA-13849) All topics whose cleanup policy contains `compact` are not executing deleteLogStartOffsetBreachedSegments as expected

RivenSun created KAFKA-13849: Summary: All topics whose cleanup policy contains `compact` are not executing deleteLogStartOffsetBreachedSegments as expected Key: KAFKA-13849 URL:

Re: [DISCUSS] KIP-821: Connect Transforms support for nested structures

Hi Tom, Thanks for taking a look at this, and for your thoughtful comments. I'll leave it up to Jorge to address most of your comments but I wanted to share a couple quick thoughts I had regarding 103 and 104. 103. Like you, I was envisioning a possible syntax for array access that used classic

Re: [VOTE] KIP-797: Accept duplicate listener on port for IPv4/IPv6

Hi Matthew, Thanks for the KIP, +1 (binding). Kind regards, Tom On Thu, 14 Apr 2022 at 12:15, Matthew de Detrich wrote: > Hi David, > > Thanks for the response. > > > 1. In the public interface section, could we spell out > the configurations that we are changing with this > KIP? The name

Re: [DISCUSS] KIP-821: Connect Transforms support for nested structures

Hi Jorge, Thanks for the KIP, especially for the examples which are super-clear. 100. The name `field.style` isn't so clear for something like ReplaceField: it's not so obvious that field.style applies to `include` and `exclude`. 101. The permitted values for `field.style` don't seem terribly

Re: [DISCUSS] KIP-827: Expose logdirs total and usable space via Kafka API

Hi Mickael, Thanks for the KIP, I can see this would be useful. I guess you could have used optional tagged fields, rather than bumping the version, but then again I don't see it being particularly advantageous in this case either. Kind regards, Tom On Tue, 19 Apr 2022 at 10:23, Divij Vaidya

[jira] [Created] (KAFKA-13848) Clients remaing connected after SASL re-authentication fails

Andras Csaki created KAFKA-13848: Summary: Clients remaing connected after SASL re-authentication fails Key: KAFKA-13848 URL: https://issues.apache.org/jira/browse/KAFKA-13848 Project: Kafka