Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.6 #166

See

[jira] [Reopened] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore

[ https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikumar reopened KAFKA-16310: --- > ListOffsets doesn't report the offset with maxTimestamp anymore >

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.7 #121

See Changes: -- [...truncated 458795 lines...] [2024-03-28T02:48:34.234Z] [2024-03-28T02:48:34.234Z] Gradle Test Run :core:test > Gradle Test Executor 94 >

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

Hi Jun, On Wed, Mar 27, 2024 at 2:26 PM Jun Rao wrote: > 55.1 How does the broker and non-leader controller know the pending voters? They are in the log. Pending voter sets are VotersRecords between the HWM and the LEO. The leader will make sure that there is at most one VoterRecord that is

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

See Changes: -- [...truncated 307913 lines...] [2024-03-27T22:56:04.656Z] Gradle Test Run :streams:test > Gradle Test Executor 88 > DefaultStateUpdaterTest >

Re: [VOTE] KIP-981: Manage Connect topics with custom implementation of Admin

Hi Omnia! Thank you for your response. I want to make sure that we both understand the motivations and designs here, and we can make a fair evaluation. > pluggable extension point Can you explain the difference? To me, both "plugin" and "pluggable extension point" refer to an API that lets

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi, Justine, Thanks for the reply. So, "dependencies" and "version-mapping" will be added to both kafka-feature and kafka-storage? Could we document that in the tool format section? Jun On Wed, Mar 27, 2024 at 4:01 PM Justine Olshan wrote: > Ok. I can remove the info from the describe

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

See

[DISCUSS] KIP-1032: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0

Hi, I'm proposing a KIP for Kafka 4.0 to upgrade to to Jakarta and JavaEE 9 APIs. This will also upgrade dependencies like Jetty and move away from the depcrated javax namespace to be in line with other libraries and frameworks. There was some initial

[jira] [Created] (KAFKA-16437) Upgrade to Jakarta and JavaEE 9 in Kafka 4.0 (KIP-1032)

Christopher L. Shannon created KAFKA-16437: -- Summary: Upgrade to Jakarta and JavaEE 9 in Kafka 4.0 (KIP-1032) Key: KAFKA-16437 URL: https://issues.apache.org/jira/browse/KAFKA-16437 Project:

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Ok. I can remove the info from the describe output. Dependencies is needed for the storage tool because we want to make sure the desired versions we are setting will be valid. Version mapping should be for both tools since we have --release-version for both tools. I was considering changing the

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

See

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi, Justine, Thanks for the reply. Having "kafka-feature dependencies" seems enough to me. We don't need to include the dependencies in the output of "kafka-feature describe". We only support "dependencies" in kafka-feature, not kafka-storage. We probably should do the same for

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

Hi, Jose, Thanks for the reply. 55.1 How does the broker and non-leader controller know the pending voters? Jun On Wed, Mar 27, 2024 at 1:03 PM José Armando García Sancio wrote: > Hi Jun, > > Thanks for the feedback. See my comments below. > > On Mon, Mar 25, 2024 at 2:21 PM Jun Rao wrote:

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

I had already included this example bin/kafka-features.sh downgrade --feature metadata.version=16 --transaction.protocol.version=2 // Throws error if metadata version is < 16, and this would be an upgrade But I have updated the KIP to explicitly say the text you mentioned. Justine On Wed, Mar

[jira] [Created] (KAFKA-16436) Online upgrade triggering and group type conversion

Dongnuo Lyu created KAFKA-16436: --- Summary: Online upgrade triggering and group type conversion Key: KAFKA-16436 URL: https://issues.apache.org/jira/browse/KAFKA-16436 Project: Kafka Issue

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi Justine, See my comment below. On Wed, Mar 27, 2024 at 1:31 PM Justine Olshan wrote: > The feature command includes the upgrade or downgrade command along with > the --release-version flag. If some features are not moving in the > direction mentioned (upgrade or downgrade) the command will

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hey Jun, Right, sorry this would be one row in an output of all the various features (transaction.protocol.version, group.coordinator.version) currently set on the cluster. If we want to know the dependencies for each of a given feature (ie transaction.protocol.versions 0, 1, 2, 3 etc) we can

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

Hi Jun, Thanks for the feedback. See my comments below. On Mon, Mar 25, 2024 at 2:21 PM Jun Rao wrote: > 54. Yes, we could include SecurityProtocol in DescribeQuorumResponse. Then, > we could include it in the output of kafka-metadata-quorum --describe. Yes, I updated the

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

See

[jira] [Resolved] (KAFKA-16428) Fix bug where config change notification znode may not get created during migration

[ https://issues.apache.org/jira/browse/KAFKA-16428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-16428. -- Resolution: Fixed > Fix bug where config change notification znode may not get created during

[jira] [Resolved] (KAFKA-16411) Correctly migrate default client quota entities in KRaft migration

[ https://issues.apache.org/jira/browse/KAFKA-16411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin McCabe resolved KAFKA-16411. -- Resolution: Fixed > Correctly migrate default client quota entities in KRaft migration >

[jira] [Created] (KAFKA-16435) Add test for KAFKA-16428

Colin McCabe created KAFKA-16435: Summary: Add test for KAFKA-16428 Key: KAFKA-16435 URL: https://issues.apache.org/jira/browse/KAFKA-16435 Project: Kafka Issue Type: Bug

[jira] [Created] (KAFKA-16434) ForeignKey INNER join does not unset join result when FK becomes null

Ayoub Omari created KAFKA-16434: --- Summary: ForeignKey INNER join does not unset join result when FK becomes null Key: KAFKA-16434 URL: https://issues.apache.org/jira/browse/KAFKA-16434 Project: Kafka

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi, Justine, It seems that we need to specify the dependencies for each feature version? Thanks, Jun On Wed, Mar 27, 2024 at 11:28 AM Justine Olshan wrote: > Hey Jun, > > So just including the dependencies for the currently set features? Along > with the supported min, max, and finalized

Re: [VOTE] KIP-1025: Optionally URL-encode clientID and clientSecret in authorization header

Thanks for checking it out Nelson. Yeah I think it makes sense to leave it for the users who want to use it for testing. On Mon, 25 Mar 2024 at 20:44, Nelson B. wrote: > Hi Doğuşcan, > > Thanks for your vote! > > Currently, the usage of TLS depends on the protocol used by the > authorization

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hey Jun, So just including the dependencies for the currently set features? Along with the supported min, max, and finalized versions? Feature: transaction.protocol.version SupportedMinVersion: 0 SupportedMaxVersion: 2 FinalizedVersionLevel: 1 Epoch: 3 Dependencies: metadata.version=4 On Wed,

[DISCUSS] KIP-1023: Follower fetch from tiered offset

Hi All, I have created KIP-1023 to introduce follower fetch from tiered offset. This feature will be helpful in significantly reducing Kafka rebalance/rebuild times when the cluster is enabled with tiered storage.

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi, Justine, Yes, something like that. We could also extend "kafka-feature describe" by adding the dependency to every feature in the output. Thanks, Jun On Wed, Mar 27, 2024 at 10:39 AM Justine Olshan wrote: > Hi Jun, > > We could expose them in a tool. I'm wondering, are you thinking

[jira] [Resolved] (KAFKA-16310) ListOffsets doesn't report the offset with maxTimestamp anymore

[ https://issues.apache.org/jira/browse/KAFKA-16310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chia-Ping Tsai resolved KAFKA-16310. Resolution: Fixed > ListOffsets doesn't report the offset with maxTimestamp anymore >

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi Jun, We could expose them in a tool. I'm wondering, are you thinking something like a command that lists the dependencies for a given feature + version? Something like: kafka-feature dependencies --feature transaction.protocol.version=2 > transaction.protocol.verison=2 requires

Re: [DISCUSS] KIP-1022 Formatting and Updating Features

Hi, Colin, Thanks for the comments. It's fine if we want to keep the --metadata flag if it's useful. Then we should add the same flag for kafka-storage for consistency, right? Hi, Justine, Thanks for the reply. How will a user know about the dependencies among features? Should we expose them

Re: [DISCUSS] Jakarta and Java EE 9/10 support in Kafka 4.0

Hi Ismael, Thanks for the feedback, I can definitely raise a KIP, that is no problem. I will write one up and then we can have further discussion on the details. I should have time to get one created later today or by tomorrow. Chris On Wed, Mar 27, 2024 at 11:54 AM Ismael Juma wrote: > Hi

[jira] [Created] (KAFKA-16433) beginningOffsets and offsetsForTimes don't behave consistently when providing a zero timeout

Philip Nee created KAFKA-16433: -- Summary: beginningOffsets and offsetsForTimes don't behave consistently when providing a zero timeout Key: KAFKA-16433 URL: https://issues.apache.org/jira/browse/KAFKA-16433

Re: [DISCUSS] KIP-477: Add PATCH method for connector config in Connect REST API

Hi Ivan, Thanks for the updates. LGTM! RE atomicity: I think it should be possible and not _too_ invasive to detect and handle these kinds of races by tracking the offset in the config topic for connector configs and aborting an operation if that offset changes between when the request was

Re: [DISCUSS] Jakarta and Java EE 9/10 support in Kafka 4.0

Hi Christopher, Thanks for raising this. Moving to the new namespace makes sense - would you be willing to submit a KIP? The point you raised regarding Jetty 11 EOL and Jetty 12 requiring Java 17 is a good one and is worth discussing the trade-offs in more detail. I originally did not propose

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

See

[jira] [Resolved] (KAFKA-16432) KStreams: Joining KStreams and GlobalKTable requires a state store

[ https://issues.apache.org/jira/browse/KAFKA-16432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matej Sprysl resolved KAFKA-16432. -- Resolution: Fixed Fixed by using the same StreamsBuilder for both streams. > KStreams:

Re: [DISCUSS] KIP-477: Add PATCH method for connector config in Connect REST API

Hi, I updated the KIP with the two following changes: 1. Using `null` values as tombstone value for removing existing fields from configuration. 2. Added a note about the lack of 100% atomicity, which seems very difficult to achieve practically. Ivan On Tue, Mar 26, 2024, at 14:45, Ivan

[jira] [Created] (KAFKA-16432) KStreams: Joining KStreams and GlobalKTable requires a state store

Matej Sprysl created KAFKA-16432: Summary: KStreams: Joining KStreams and GlobalKTable requires a state store Key: KAFKA-16432 URL: https://issues.apache.org/jira/browse/KAFKA-16432 Project: Kafka

Re: [VOTE] KIP-981: Manage Connect topics with custom implementation of Admin

Hi Greg thanks for the feedback and sorry for the late response. > I don't think we can adapt the ForwardingAdmin as-is for use as a > first-class Connect plugin. > 1. It doesn't have a default constructor, and so can't be included in > the existing plugin discovery mechanisms. > 2. It doesn't

Re: Permission to assign tickets in Jira

Hi Pavel, I've granted you the necessary permissions. Thanks for your interest in contributing to the Apache Kafka project! Cheers, Yash On Tue, Mar 26, 2024 at 11:32 PM Pavel Pozdeev wrote: > > Hi Team, > > Would it be possible to get a permission to assign tickets in Jira? > I've got a Jira

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

See

[jira] [Resolved] (KAFKA-16403) Flaky test org.apache.kafka.streams.examples.wordcount.WordCountDemoTest.testCountListOfWords

[ https://issues.apache.org/jira/browse/KAFKA-16403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Soarez resolved KAFKA-16403. - Resolution: Not A Bug > Flaky test >

[jira] [Resolved] (KAFKA-16404) Flaky test org.apache.kafka.streams.examples.wordcount.WordCountDemoTest.testGetStreamsConfig

[ https://issues.apache.org/jira/browse/KAFKA-16404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Igor Soarez resolved KAFKA-16404. - Resolution: Not A Bug Same as KAFKA-16403, this only failed once. It was likely the result of a

[jira] [Resolved] (KAFKA-16353) Offline protocol migration integration tests

[ https://issues.apache.org/jira/browse/KAFKA-16353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-16353. - Resolution: Fixed > Offline protocol migration integration tests >

Community Over Code NA 2024 Travel Assistance Applications now open!

Hello to all users, contributors and Committers! [ You are receiving this email as a subscriber to one or more ASF project dev or user mailing lists and is not being sent to you directly. It is important that we reach all of our users and contributors/committers so that they may get a chance

Re: [ANNOUNCE] New committer: Christo Lolov

Congrats! On 3/26/24 9:39 PM, Christo Lolov wrote: Thank you everyone! It wouldn't have been possible without quite a lot of reviews and extremely helpful inputs from you and the rest of the community! I am looking forward to working more closely with you going forward :) On Tue, 26 Mar 2024

[jira] [Created] (KAFKA-16430) The group-metadata-manager thread is always in a loading state and occupies one CPU, unable to end.

Gao Fei created KAFKA-16430: --- Summary: The group-metadata-manager thread is always in a loading state and occupies one CPU, unable to end. Key: KAFKA-16430 URL: https://issues.apache.org/jira/browse/KAFKA-16430

[jira] [Created] (KAFKA-16429) Enhance all configs which can trigger rolling of new segment

Chia-Ping Tsai created KAFKA-16429: -- Summary: Enhance all configs which can trigger rolling of new segment Key: KAFKA-16429 URL: https://issues.apache.org/jira/browse/KAFKA-16429 Project: Kafka