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

See

Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

> > I missed the default config values as they were put into comments... You don't read code comments? (jk...sorry, wasn't sure where the best place for this would be, suppose I could've just included the full config definition About the default timeout: what is the follow up rebalance

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

See

[jira] [Created] (KAFKA-14439) Specify returned errors for various APIs and versions

Justine Olshan created KAFKA-14439: -- Summary: Specify returned errors for various APIs and versions Key: KAFKA-14439 URL: https://issues.apache.org/jira/browse/KAFKA-14439 Project: Kafka

RE: Re: RE: Re: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Thanks for the reply, 04. `nullable-string`, my mistake on that — this is the representation I have for nullable strings in my own DSL in franz-go. I’ve fixed that. 05. I think that ClusterSoftwareVersion and ClusterSoftwareName would be a bit odd: technically these are per-broker responses,

[jira] [Created] (KAFKA-14438) Stop supporting empty consumer groupId

Philip Nee created KAFKA-14438: -- Summary: Stop supporting empty consumer groupId Key: KAFKA-14438 URL: https://issues.apache.org/jira/browse/KAFKA-14438 Project: Kafka Issue Type: Task

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

See Changes: -- [...truncated 541343 lines...] [2022-12-02T21:06:37.259Z] Gradle Test Run :streams:integrationTest > Gradle Test Executor 169 >

[jira] [Resolved] (KAFKA-6643) Warm up new replicas from scratch when changelog topic has LIMITED retention time

[ https://issues.apache.org/jira/browse/KAFKA-6643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6643. Resolution: Won't Fix > Warm up new replicas from scratch when changelog topic has LIMITED

[jira] [Resolved] (KAFKA-6542) Tables should trigger joins too, not just streams

[ https://issues.apache.org/jira/browse/KAFKA-6542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6542. Resolution: Invalid This will be fixed via versioned stores and "delayed table lookups".

[jira] [Resolved] (KAFKA-6509) Add additional tests for validating store restoration completes before Topology is intitalized

[ https://issues.apache.org/jira/browse/KAFKA-6509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-6509. Resolution: Not A Problem > Add additional tests for validating store restoration

[jira] [Resolved] (KAFKA-5245) KStream builder should capture serdes

[ https://issues.apache.org/jira/browse/KAFKA-5245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5245. Resolution: Fixed > KStream builder should capture serdes >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #130

See Changes: -- [...truncated 417711 lines...] [2022-12-02T19:29:16.239Z] [INFO] --- maven-gpg-plugin:1.6:sign (sign-artifacts) @ streams-quickstart-java ---

[jira] [Resolved] (KAFKA-5085) Add test for rebalance exceptions

[ https://issues.apache.org/jira/browse/KAFKA-5085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-5085. Resolution: Abandoned Might no be necessary any longer given all the changes we did over

[GitHub] [kafka-site] C0urante commented on pull request #463: MINOR: Add new signing key for Chris Egerton

C0urante commented on PR #463: URL: https://github.com/apache/kafka-site/pull/463#issuecomment-1335655739 Thanks Bill! -- 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 specific comment. To

[GitHub] [kafka-site] C0urante merged pull request #463: MINOR: Add new signing key for Chris Egerton

C0urante merged PR #463: URL: https://github.com/apache/kafka-site/pull/463 -- 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 specific comment. To unsubscribe, e-mail:

Re: [DISCUSS] KIP-890 Server Side Defense

Hey Matthias, 20/30 — Maybe I also didn't express myself clearly. For older clients we don't have a way to distinguish between a previous and the current transaction since we don't have the epoch bump. This means that a late message from the previous transaction may be added to the new one. With

RE: Kafka support for TLSv1.3

Hi Ismael, Thanks for the quick response. Are there any plans in future anytime soon to support latest versions of Kafka over TLSv1.3 with Java8u261 and above? If yes, by when can we expect that. Regards Deepak Nangia From: Ismael Juma Sent: 02 December 2022 23:27 To: us...@kafka.apache.org

[GitHub] [kafka-site] C0urante opened a new pull request, #463: MINOR: Add new signing key for Chris Egerton

C0urante opened a new pull request, #463: URL: https://github.com/apache/kafka-site/pull/463 This key can also be found on keys.openpgp.org with an ID of ceger...@apache.org. This is being uploaded in preparation of the 3.3.2 release. -- This is an automated message from the

Re: Kafka support for TLSv1.3

Hi Deepak, Kafka currently only supports TLS 1.3 with Java 11 or newer. As you said, Kafka 2.6 added support for it, but we recommend using something more recent as there were some fixes after the original release. Ismael On Fri, Dec 2, 2022 at 7:21 AM Deepak Nangia wrote: > Hello All, > > I

Re: [DISCUSS] KIP-888: Batch describe ACLs and describe client quotas

Hi Mickael, Thanks for the KIP. I can understand the motivation, but to be honest I have a doubt about this. Taking the ACLs first, by allowing multiple filters with the current proposal isn't there the chance that the same ACL will match multiple filters, and be returned multiple times in the

Re: RE: Re: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Yeah, it is too late for 3.4. I have a few more comments: 04. `nullable-string` is not a valid type. You have to use "type": "string", "versions": "1+", "nullableVersions": "1+". 05. BrokerSoftwareName/BrokerSoftwareVersion feel a bit weird in a DescribeClusterResponse. I wonder if we should

Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

Thanks Sophie. Good catch on the default partitioner issue! I missed the default config values as they were put into comments... About the default timeout: what is the follow up rebalance cadence (I though it would be 10 minutes?). For this case, a default timeout of 15 minutes would imply

RE: RE: Re: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

I see now that this KIP is past the freeze deadline and will not make 3.4 — but, 3.4 thankfully will still be able to be detected by an ApiVersions response due to KIP-866. I’d like to proceed with this KIP to ensure full implementation can be agreed upon and merged by 3.5. Thanks! - Travis

RE: Re: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Hi David, No worries for the late reply — my main worry is getting this in by Kafka 3.4 so there is no gap in detecting versions :) I’m +1 to adding this to DescribeCluster. I just edited the KIP to replace ApiVersions with DescribeCluster, and added the original ApiVersions idea to the list

[jira] [Resolved] (KAFKA-14358) Users should not be able to create a regular topic name __cluster_metadata

[ https://issues.apache.org/jira/browse/KAFKA-14358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] José Armando García Sancio resolved KAFKA-14358. Resolution: Fixed > Users should not be able to create a regular

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

See

Re: [DISCUSS] Apache Kafka 3.4.0 release

Hi Sophie, FYI - I just merged KIP-840 (https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=211884652) so it will be in 3.4. Best, David On Thu, Dec 1, 2022 at 3:01 AM Sophie Blee-Goldman wrote: > > Hey all! It's officially *feature freeze for 3.4* so make sure you get that >

Re: [DISCUSS] KIP-878: Autoscaling for Statically Partitioned Streams

Thanks again for the responses -- just want to say up front that I realized the concept of a default partitioner is actually substantially more complicated than I first assumed due to key/value typing, so I pulled it from this KIP and filed a ticket for it for now. Bruno, What is exactly the

Re: RE: Re: [DISCUSS] KIP-885: Expose Broker's Name and Version to Clients Skip to end of metadata

Hi Travis, Please, excuse me for my late reply. 02. Yeah, I agree that it is more convenient to rely on the api versions but that does not protect us from misuages. 03. Yeah, I was about to suggest the same. Adding the information to the DescribeCluster API would work and we also have the

[jira] [Created] (KAFKA-14436) Initialize KRaft with arbitrary epoch

David Arthur created KAFKA-14436: Summary: Initialize KRaft with arbitrary epoch Key: KAFKA-14436 URL: https://issues.apache.org/jira/browse/KAFKA-14436 Project: Kafka Issue Type: Sub-task

Kafka log segments recovery on startup

Hello, Can anyone please point to any docs re how replica recovery works when broker is started?  The documentation has information about broker rebuilding based on data on data dir- but what happens if data is completely lost? Would an empty replica be created based on zookeeper state- and if

Kafka support for TLSv1.3

Hello All, I have few queries regarding Kafka support for TLSv1.3 as below: 1. Which Kafka version and above support TLSv1.3 * In latest Kafka release notes, I see that TLSv1.3 has been introduced in Kafka 2.6.0 and above.

[jira] [Resolved] (KAFKA-14433) Clear all yammer metrics when test harnesses clean up

[ https://issues.apache.org/jira/browse/KAFKA-14433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Arthur resolved KAFKA-14433. -- Resolution: Fixed > Clear all yammer metrics when test harnesses clean up >

[jira] [Created] (KAFKA-14435) Kraft: StandardAuthorizer allowing a non-authorized user when `allow.everyone.if.no.acl.found` is enabled

Purshotam Chauhan created KAFKA-14435: - Summary: Kraft: StandardAuthorizer allowing a non-authorized user when `allow.everyone.if.no.acl.found` is enabled Key: KAFKA-14435 URL:

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

See Changes: -- [...truncated 467797 lines...] [2022-12-02T08:52:15.762Z] > Task :clients:publishMavenJavaPublicationToMavenLocal [2022-12-02T08:52:15.762Z] > Task

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.3 #129

See Changes: -- [...truncated 416946 lines...] [2022-12-02T07:22:39.193Z] org.apache.kafka.streams.integration.SuppressionIntegrationTest > shouldCreateChangelogByDefault

[jira] [Resolved] (KAFKA-14400) KStream - KStream - LeftJoin() does not call ValueJoiner with null value

[ https://issues.apache.org/jira/browse/KAFKA-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Victor van den Hoven resolved KAFKA-14400. -- Resolution: Not A Bug It behaves differently because stream-stram-leftjoin