[jira] [Resolved] (KAFKA-16751) Implement release acquired records in SharePartitionManager

[ https://issues.apache.org/jira/browse/KAFKA-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Dixit resolved KAFKA-16751. --- Fix Version/s: 4.0.0 3.9.0 Resolution: Fixed > Implement release a

[jira] [Created] (KAFKA-17044) Connector worker does not shutdown until start completes

Bhagyashree created KAFKA-17044: --- Summary: Connector worker does not shutdown until start completes Key: KAFKA-17044 URL: https://issues.apache.org/jira/browse/KAFKA-17044 Project: Kafka Issue

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

Hi all, I want to bring up this thread once more. I am hoping to include this KIP in the 3.9.0 release. The KIP freeze is on July 3rd (next Wednesday), so it would be great if we could finalize the vote by then. We are targeting the 3.9.0 release because we plan to piggyback on KIP-1030 and chang

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

See

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi Justine, I did not update the KIP with `TxnSendOption` since I thought it'd be better discussed here beforehand. right now, there are 2 PRs: - the PR that implements the current version of the KIP: https://github.com/apache/kafka/pull/16332 - the POC PR that clarifies the `TxnSendOption`: https

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

See Changes: -- [...truncated 3.47 MB...] org.apache.kafka.streams.TestTopicsTest > testDuration PASSED org.apache.kafka.streams.TestTopicsTest > testOutputToString STARTED

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

Hi Jun, KIP-1014 is explicitly NOT for EA features, since EA features need to be usable by non-developers. I think it's important to be clear about this. Maybe "unreleased" would be a better name than "unstable" since people seem to have lots of different ideas about what "unstable" means, whi

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hey Alieh, I think I am a little confused. Are the 3 points above addressed by the KIP or did something change? The PR seems to not include this change and still has the CommitOption as well. Thanks, Justine On Wed, Jun 26, 2024 at 2:15 PM Alieh Saeedi wrote: > Hi all, > > > Looking at the PR

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

Hi, Colin, Thanks for the reply. 4. "A developer could modify the code to allow unstable features outside of JUnit, and then run whatever they want." Hmm, it's inconvenient for a developer to make some temporary change just to test an unstable feature outside of junit, right? Also, how does a us

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi all, Looking at the PR corresponding to the KIP, there are some points worthy of mention: 1) clearing the error ends up dirty/messy code in `TransactionManager`. 2) By clearing the error, we are actually doing an illegal transition from `ABORTABL

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

On Wed, Jun 26, 2024, at 13:16, Jun Rao wrote: > Hi, Colin, > > Thanks for the reply. > > 1. https://kafka.apache.org/protocol.html#The_Messages_ConsumerGroupDescribe > lists ConsumerGroupDescribeRequest, whose latest version is unstable. > Hi Jun, I think that is a bug. > > 4. "As devlopers, th

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

Thanks for the reply, Justine and Colin. Sounds good to me. Jun On Wed, Jun 26, 2024 at 12:54 PM Colin McCabe wrote: > Hi Justine, > > Yes, that was what I was thinking. > > best, > Colin > > On Mon, Jun 24, 2024, at 11:11, Justine Olshan wrote: > > My understanding is that the tools that don't

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

Hi, Colin, Thanks for the reply. 1. https://kafka.apache.org/protocol.html#The_Messages_ConsumerGroupDescribe lists ConsumerGroupDescribeRequest, whose latest version is unstable. 4. "As devlopers, they can change the code to do this if they want." Just to be clear. A developer could be able to

[jira] [Created] (KAFKA-17043) Strictly Uniform Sticky partition strategy leads to slow handling of command events

Timur created KAFKA-17043: - Summary: Strictly Uniform Sticky partition strategy leads to slow handling of command events Key: KAFKA-17043 URL: https://issues.apache.org/jira/browse/KAFKA-17043 Project: Kafka

Re: [DISCUSS] Apache Kafka 3.9.0 release

Hi Mario and Nelson, Thanks for asking. Both of these KIPs can certainly go in 3.9 if we can hit the deadlines. If you need an extra day or two just ping me. (But I don't want to extend things for too long!) :) Do we feel that KIP-1040 can make feature freeze? best, Colin On Tue, Jun 25, 2024

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

Hi Justine, Yes, that was what I was thinking. best, Colin On Mon, Jun 24, 2024, at 11:11, Justine Olshan wrote: > My understanding is that the tools that don't rely on ApiVersions should > still return 0s when it is the correct value. I believe these commands do > not require this API and thus

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

On Wed, Jun 26, 2024, at 12:09, Jun Rao wrote: > Hi, Colin, > > Thanks for restarting the discussion. A few comments. > > 1. "An unstable RPC version can be changed at any time, until it becomes > stable." > > What's our recommendation to non-java developers? Should they start > building a new vers

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

Hi Justine, Since these configurations are (and have always been) internal, changing or removing them should be no problem. best, Colin On Tue, Jun 25, 2024, at 16:51, Justine Olshan wrote: > Hey Colin, > > I made a single configuration as part of KIP-1022 called > unstableFeatureVersionsEnable

Re: [DISCUSS] KIP-1014: Managing Unstable Features in Apache Kafka

Hi, Colin, Thanks for restarting the discussion. A few comments. 1. "An unstable RPC version can be changed at any time, until it becomes stable." What's our recommendation to non-java developers? Should they start building a new version of an RPC until it is stable? Should we explicitly mark u

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

See

[jira] [Created] (KAFKA-17042) the migration docs should remind users to set "broker.id.generation.enable" when adding broker.id

Chia-Ping Tsai created KAFKA-17042: -- Summary: the migration docs should remind users to set "broker.id.generation.enable" when adding broker.id Key: KAFKA-17042 URL: https://issues.apache.org/jira/browse/KAFKA-17

Re: [VOTE] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi Alieh, Thanks for the KIP. I think we’ve settled on a good solution. +1 (non-binding) Thanks, Andrew > On 25 Jun 2024, at 13:17, Alieh Saeedi wrote: > > Hi all, > > I would like to open voting for KIP-1059: Enable the Producer flush() > method to clear the latest send() error >

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi all, thanks for the brilliant ideas. The KIP is updated as follows: -Regarding the word "latest”: I chose this word because in documentation of the `commitTnx()`, it is clearly mentioned that the method throws the lates exception of `send()`. BTW, I agree with you to change it to “any” since “

[jira] [Created] (KAFKA-17041) Add pagination when describe large set of metadata via Admin API

Omnia Ibrahim created KAFKA-17041: - Summary: Add pagination when describe large set of metadata via Admin API Key: KAFKA-17041 URL: https://issues.apache.org/jira/browse/KAFKA-17041 Project: Kafka

[jira] [Resolved] (KAFKA-17003) Implement SharePartitionManager close functionality

[ https://issues.apache.org/jira/browse/KAFKA-17003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhinav Dixit resolved KAFKA-17003. --- Fix Version/s: 4.0.0 3.9.0 Resolution: Fixed > Implement SharePart

Re: [DISCUSS] KIP-1057: Add remote log metadata flag to the dump log tool

Thank you Federico for answering the questions. No more questions/concerns from me. The KIP looks good. -- Divij Vaidya On Wed, Jun 26, 2024 at 11:02 AM Federico Valeri wrote: > Hi Divij, thanks for you questions and suggestions, much appreciated. > > On Tue, Jun 25, 2024 at 1:12 PM Divij Vai

Re: [DISCUSS] KIP-1057: Add remote log metadata flag to the dump log tool

Hi Divij, thanks for you questions and suggestions, much appreciated. On Tue, Jun 25, 2024 at 1:12 PM Divij Vaidya wrote: > > Hey all > > Seems like we have quite a lot of interest in adding this dedicated flag in > addition to existing alternatives. In that case, I will cede to the > majority in

Re: [DISCUSS] KIP-1059: Enable the Producer flush() method to clear the latest send() error

Hi, Looking at your suggestions for the CommitOptions, I would be happy with either. I definitely prefer to the Map in the KIP. We also need to think about the other option where CLEAR_SEND_ERRORS hasn’t been specified, and leave ourselves space for other options in the future. If we use an enum,