[jira] [Created] (KAFKA-17415) Avoid overflow of expiried timestamp

Chia-Ping Tsai created KAFKA-17415: -- Summary: Avoid overflow of expiried timestamp Key: KAFKA-17415 URL: https://issues.apache.org/jira/browse/KAFKA-17415 Project: Kafka Issue Type: Bug

Re: [DISCUSS] KIP-1075: Introduce delayed remote list offsets purgatory to make LIST_OFFSETS async

Hi Jun, Thanks for the review! 1. purgatoryName = RemoteListOffsets 2. We want to emit the metric at the partition level. Thanks for catching this! Updated the public interfaces section in the KIP! -- Kamal On Sat, Aug 24, 2024 at 3:14 AM Jun Rao wrote: > Hi, Kamal, > > Thanks for the KIP. J

Re: [DISCUSS] KIP-512: make Record Headers available in onAcknowledgement

hi Rich > Header.lastHeader(Iterable)? That’s an interesting idea, but I think it falls outside the scope of this KIP. If you’re interested, perhaps you could start another discussion thread or raise a separate KIP for it. The APIs included by this KIP is public, and so we can't change it easily

Re: [VOTE] KIP-512: make Record Headers available in onAcknowledgement and onComplete

+1 (binding) On 2024/08/10 17:28:45 "Rich C." wrote: > Hi all, > > After incorporating the feedback received > , I have > updated KIP-512 to reflect the majority preference for the new interface > approach. The KIP is now in its fi

Re: [DISCUSS] KIP-512: make Record Headers available in onAcknowledgement

Hi Chia-Ping, > be we can add public helpers to Header to offer “last header”? The helper can cast the Iterable to List (if ok) to get last header effectively Are you referring to extracting the RecordHeaders#lastHeader()

RE: [VOTE] KIP-1052: Enable warmup in producer performance test

Hi Kafka devs, Bumping this VOTE thread for visibility. Thanks, Matt -Original Message- From: Federico Valeri Sent: Monday, August 19, 2024 12:38 AM To: dev@kafka.apache.org Subject: Re: [VOTE] KIP-1052: Enable warmup in producer performance test Hi Matt, +1 (non binding) from me. Th

Re: [DISCUSS] KIP-1075: Introduce delayed remote list offsets purgatory to make LIST_OFFSETS async

Hi, Kamal, Thanks for the KIP. Just a couple of minor comments. Since we use the purgatory name as the metric tag, could you spell out the exact new purgatory name for remote list offset? private val metricsTags = Map("delayedOperation" -> purgatoryName).asJava metricsGroup.newGauge("Purgator

[jira] [Resolved] (KAFKA-17404) Return the actual controller id or -1 instead of a random broker id when calling DescribeCluster or TopicMetadata APIs. .

[ https://issues.apache.org/jira/browse/KAFKA-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nelson B. resolved KAFKA-17404. --- Resolution: Not A Problem > Return the actual controller id or -1 instead of a random broker id when

Re: [DISCUSS] Apache Kafka 3.9.0 release

Hi Loic, I think I responded in another thread, but just to close the loop here, KIP-1033 is indeed in 3.9. regards, Colin On Mon, Jul 22, 2024, at 08:13, Loic Greffier wrote: > Hello, > > Can KIP-1033 > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1033%3A+Add+Kafka+Streams+exception

Re: [VOTE] KIP-1042: Support for wildcard when creating new acls

On Sat, Jul 27, 2024, at 04:20, Claude Warren, Jr wrote: > I have updated the KIP with results from the Trie implementation and they > are dramatic to say the least. For most searches they are at least an > order of magnitude faster and use less memory. The wildcard search is not > a regular expr

Re: New release branch 3.9

I wanted to give a quick update on 3.9. Code freeze is coming up next Thursday on the 29th. As usual, after that point, only critical bug fixes will be accepted. Thanks again to everyone who has helped with this release. best, Colin On Fri, Aug 23, 2024, at 13:18, Colin McCabe wrote: > Thanks

Re: New release branch 3.9

Thanks for the heads up, Josep. I saw both emails but I didn't make the connection until now. It does seem likely that we'll have to modify this (either for 3.9... or soon.) best, Colin On Tue, Aug 13, 2024, at 05:09, Josep Prat wrote: > Hi Colin, > > Just to make sure you (as a Release Manager

Re: [PR] MINOR: Add CVE-2024-27309 [kafka-site]

cmccabe commented on PR #621: URL: https://github.com/apache/kafka-site/pull/621#issuecomment-2307751152 Thanks for fixing this, @mimaison . -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the sp

Re: Question about ResourcePatternFilter

Hi Claude, As I recall, the intention was that if PatternType is ANY, the name field would simply be ignored. Probably we should have thrown an exception if someone tried to create a ResourcePatternFilter with a non-null name and PatternType ANY. best, Colin On Tue, Aug 20, 2024, at 04:19, Cl

[jira] [Resolved] (KAFKA-12818) Memory leakage when kafka connect 2.7 uses directory config provider

[ https://issues.apache.org/jira/browse/KAFKA-12818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Greg Harris resolved KAFKA-12818. - Resolution: Duplicate > Memory leakage when kafka connect 2.7 uses directory config provider > -

[jira] [Resolved] (KAFKA-17291) Add integration test for share group list and describe admin calls

[ https://issues.apache.org/jira/browse/KAFKA-17291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Schofield resolved KAFKA-17291. -- Resolution: Fixed > Add integration test for share group list and describe admin calls

Re: [DISCUSS] KIP-1081: Graduation Steps for Features

On Thu, Aug 22, 2024, at 07:36, Andrew Schofield wrote: > Hi Josep, > Thanks for creating this KIP. It looks like a good proposal. A few comments. > > AS1: I don’t think features should be able to progress between the levels in > patch releases. Yes, there may be some bug fixes which mean that > th

Re: [DISCUSS] KIP-1081: Graduation Steps for Features

Hi Josep, Thanks for the KIP. >From a user's point of view, I don't see what the difference is between level >1 and level 2. Both are not completed, not API stable, not able to be used in >production, not enabled by default. The release manager's view is similar to >the user's point of view in

Re: Idempotency impact on Kafka performance.

Yes it does, but not my much. Cf https://www.confluent.io/blog/exactly-once-semantics-are-possible-heres-how-apache-kafka-does-it/ On 8/23/24 1:42 AM, Abhijit Dutta wrote: Hi, A quick clarification - Does enabling idempotency feature in Kafka affect the throughput. Has any benchmark bee

Re: [DISCUSS] KIP-891: Running multiple versions of Connector plugins

Hi Greg, Thanks for the clarification! I agree with not breaking compatibility and opting to not fail worker startup by validating converter versions. Let's also go with the unclosed variation of the requirements as a hard requirement i.e. 3.8 instead of [3.8]. I have updated the KIP and added a

[jira] [Created] (KAFKA-17414) Move RequestLocal to server-common module

Dmitry Werner created KAFKA-17414: - Summary: Move RequestLocal to server-common module Key: KAFKA-17414 URL: https://issues.apache.org/jira/browse/KAFKA-17414 Project: Kafka Issue Type: Sub-t

[jira] [Created] (KAFKA-17413) Re-introduce `group.version` feature flag

David Jacot created KAFKA-17413: --- Summary: Re-introduce `group.version` feature flag Key: KAFKA-17413 URL: https://issues.apache.org/jira/browse/KAFKA-17413 Project: Kafka Issue Type: Sub-task

[jira] [Resolved] (KAFKA-16379) Coordinator flush time and event purgatory time metrics

[ https://issues.apache.org/jira/browse/KAFKA-16379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16379. - Fix Version/s: 4.0.0 Resolution: Fixed > Coordinator flush time and event purgatory time

[jira] [Created] (KAFKA-17412) Doc the different behavior of `unclean.leader.election.enable` in KRaft

Luke Chen created KAFKA-17412: - Summary: Doc the different behavior of `unclean.leader.election.enable` in KRaft Key: KAFKA-17412 URL: https://issues.apache.org/jira/browse/KAFKA-17412 Project: Kafka

[jira] [Resolved] (KAFKA-17193) Pin external GitHub actions to specific git hash

[ https://issues.apache.org/jira/browse/KAFKA-17193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Maison resolved KAFKA-17193. Fix Version/s: 4.0.0 Resolution: Fixed > Pin external GitHub actions to specific gi

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.4 #178

See Changes: -- [...truncated 531752 lines...] [2024-08-23T10:08:34.475Z] [2024-08-23T10:08:34.475Z] Gradle Test Run :core:integrationTest > Gradle Test Executor 172 > Fetch

[jira] [Created] (KAFKA-17411) StateStore managed changelog offsets

Nicholas Telford created KAFKA-17411: Summary: StateStore managed changelog offsets Key: KAFKA-17411 URL: https://issues.apache.org/jira/browse/KAFKA-17411 Project: Kafka Issue Type: Impr

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.6 #178

See Changes: -- [...truncated 306950 lines...] [2024-08-23T05:13:05.482Z] [2024-08-23T05:13:05.482Z] Gradle Test Run :streams:test > Gradle Test Executor 62 > DefaultStateUp

Idempotency impact on Kafka performance.

Hi, A quick clarification - Does enabling idempotency feature in Kafka affect the throughput. Has any benchmark been done till now? Ref:https://stackoverflow.com/questions/64939661/does-enabling-idempotence-on-a-kafka-producer-decrease-throughput Thanks Abhijit

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.5 #112

See

Re: [DISCUSS] KIP-1079: Deprecate `delete-config` of TopicCommand

Hello folks, I believe this KIP is finalized and ready for a vote. If there are no further discussions, I will proceed with filing a vote soon. Best regards, TengYao TengYao Chi 於 2024年8月5日 週一 下午10:57寫道： > Hello folks, > I think we have reached a consensus, and we can now see if there are any

Re: [DISCUSS] KIP-1081: Graduation Steps for Features

Hi Andrew, thanks for the feedback! AS1: I'm fine with it. Updated the KIP. AS2: I think both steps are needed. I agree with you that KIP authors should keep the release plan page up-to-date with the status of their KIP. However, as a user of the KIP, having a graduation steps log would help und

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

See