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

See

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hi Artem, Thanks for the update. I have some questions about it: 1. Could you explain why you need the `partitioner` return -1? In which case we need it? And how it is used in your KIP? 2. What does the "partitioner.sticky.batch.size" mean? In the "Configuration" part, you didn't explain it. And

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

See

Re: Newbie - Contributor

Hi Raju, Thanks for the interest in Kafka. I've added you into kafka JIRA dev list. You can start to assign jira tickets to yourselves. BTW, you don't have to attach the linkedin page. Everyone is welcome to contribute to Kafka. :) Luke On Wed, Feb 16, 2022 at 10:03 AM Bangarraju Vadapalli <

[jira] [Created] (KAFKA-13670) Consume in assign mode, If the group is null, the consumption can still be performed

shouzuo meng created KAFKA-13670: Summary: Consume in assign mode, If the group is null, the consumption can still be performed Key: KAFKA-13670 URL: https://issues.apache.org/jira/browse/KAFKA-13670

Newbie - Contributor

Dear Kafka Dev Team, I am Raju, and would like to start contributing to Kafka Project bugs and enhancements. Would like to start with newbie development work. Can you pls add my jira user id: raju1712 to kafka dev list, so that i can start contributing. Just in case, if you want to look at

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

See

Re: [DISCUSS] KIP-813 Shared State Stores

Thanks for updating the KIP. Could you add more details about the signature of `addReadOnlyStateStore()` -- What parameters does it take? Are there any overloads taking different parameters? The KIP only contains some verbal description on the "Implementation Plan" section, that is hard to

Re: [DISCUSS] KIP-794: Strictly Uniform Sticky Partitioner

Hello, Please add your comments about the KIP. If there are no considerations, I'll put it up for vote in the next few days. -Artem On Mon, Feb 7, 2022 at 6:01 PM Artem Livshits wrote: > Hello, > > After trying a few prototypes, I've made some changes to the public > interface. Please see

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

Thanks for the KIP. In alignment to my reply to KIP-634, I am wondering if we are heading into the right direction, or if we should consider to re-design the DSL from scratch? Even if we don't do a DSL 2.0 right now, I have some concerns about this KIP: (1) I am not sure if the propose

Re: [DISCUSS] KIP-634: Complementary support for headers in Kafka Streams DSL

Sorry for playing devil's advocate, but do we really think it's a good way to design the API? To me, if feels like a cumbersome workaround. Personally, I believe that we are hitting a point for the DSL that requires a redesign from scratch. When the DSL was designed 5 years ago, record

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

See

Re: [External] Gigantic list of Avro spec issues

I am not an Avro expert, but here are some thoughts: In general, I think you should submit a PR or PRs to suggest improvements, unless you are unsure what change should be made. That seems more productive than a list of things that you think are "stupid". Another possibility would be putting

[jira] [Created] (KAFKA-13669) Log messages for source tasks with no offsets to commit are noisy and confusing

Chris Egerton created KAFKA-13669: - Summary: Log messages for source tasks with no offsets to commit are noisy and confusing Key: KAFKA-13669 URL: https://issues.apache.org/jira/browse/KAFKA-13669

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

See

Re: Gigantic list of Avro spec issues

Hi Askar This is certainly an extensive list. I wanted to email you just to let you know that *someone* has seen it. Though I can't speak to all of it, I do have a few of my own impressions: > How it is happened that such good format has so bad spec? How it is happened that *best* format for

[jira] [Created] (KAFKA-13668) Failed cluster authorization should not be fatal for producer

Jason Gustafson created KAFKA-13668: --- Summary: Failed cluster authorization should not be fatal for producer Key: KAFKA-13668 URL: https://issues.apache.org/jira/browse/KAFKA-13668 Project: Kafka

Re: [DISCUSS] KIP-634: Complementary support for headers in Kafka Streams DSL

Thanks for the update, Jorge, I've just looked over the KIP again. Just one more small concern: 5) We can't just change the type of Record#headers() to a new fully qualified type. That would be a source- incompatible breaking change for users. Out options are: * Deprecate the existing method

Re: [VOTE] KIP-820: Extend KStream process with new Processor API

Thanks, Jorge! I'm +1 (binding) -John On Tue, 2022-02-15 at 19:16 +, Jorge Esteban Quilcate Otoya wrote: > Hi all, > > I'd like to start a vote on KIP-820 which proposes extending KStream to use > the new Processor API >

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

My apologies, this feedback was intended for KIP-634. -John On Tue, Feb 15, 2022, at 13:15, John Roesler wrote: > Thanks for the update, Jorge, > > I've just looked over the KIP again. Just one more small > concern: > > 5) We can't just change the type of Record#headers() to a > new fully

[VOTE] KIP-634: Complementary support for headers and record metadata in Kafka Streams DSL

Hi all, I'd like to start a vote on KIP-634 which proposes extending support for Headers and Record Metadata in Kafka Streams https://cwiki.apache.org/confluence/display/KAFKA/KIP-634%3A+Complementary+support+for+headers+and+record+metadata+in+Kafka+Streams+DSL Thanks, Jorge

[VOTE] KIP-820: Extend KStream process with new Processor API

Hi all, I'd like to start a vote on KIP-820 which proposes extending KStream to use the new Processor API https://cwiki.apache.org/confluence/display/KAFKA/KIP-820%3A+Extend+KStream+process+with+new+Processor+API Thanks, Jorge

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

Thanks for the update, Jorge, I've just looked over the KIP again. Just one more small concern: 5) We can't just change the type of Record#headers() to a new fully qualified type. That would be a source- incompatible breaking change for users. Out options are: * Deprecate the existing method

Re: [DISCUSS] KIP-820: Extend KStream process with new Processor API

Thanks Paul, this is very helpful. Glad to know this will be potentially helpful for your team moving forward. Also, thanks everyone for your feedback so far. If there's no additional questions about the current state of this KIP, I'll be starting a vote thread soon. Happy to keep discussing the

[GitHub] [kafka-site] bbejeck merged pull request #398: Update logo of Streaming Audio podcast

bbejeck merged pull request #398: URL: https://github.com/apache/kafka-site/pull/398 -- 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] Apache Kafka 3.2.0 release

Hi Bruno, Thanks for publishing the release plan! Can we add KIP-769 to the plan? Thanks, Mickael On Tue, Feb 15, 2022 at 12:37 PM Bruno Cadonna wrote: > > Hi all, > > I published a release plan for the Apache Kafka 3.2.0 release here: >

Re: [VOTE] KIP-769: Connect APIs to list all connector plugins and retrieve their configuration definitions

I'm +1 (binding) too The vote passes with: - 3 +1 (binding) votes from Tom, John and myself - 5 +1 (non-binding) from Chris, Ryanne, Viktor, Julien and Dongjin Thanks for the votes and feedback On Tue, Feb 15, 2022 at 6:54 PM Mickael Maison wrote: > > Hi Chris, > > Yes committers are allowed

Re: [VOTE] KIP-769: Connect APIs to list all connector plugins and retrieve their configuration definitions

Hi Chris, Yes committers are allowed to vote on their KIPs. I try to avoid doing it if I don't have to. Thanks, Mickael On Fri, Feb 11, 2022 at 8:38 PM John Roesler wrote: > > +1 (binding) > > Thanks, > John > > On Fri, Feb 11, 2022, at 08:43, Dongjin Lee wrote: > > +1 (non-binding) > > > >

Re: [DISCUSS] KIP-816: Topology changes without local state reset

In the KIP, for Option A I suggested a new path of: /state/dir/stores// I made the mistake of thinking that the rocksdb/ segment goes *after* the store name in the current scheme, e.g. /state/dir//[/rocksdb] This is a mistake. I'd always intended for a combination of the store name and

Re: [DISCUSS] KIP-812: Introduce another form of the `KafkaStreams.close()` API that forces the member to leave the consumer group

Hi Guozhang, Thanks a lot for sharing your idea and guiding me. Thanks to your support, we've reached this voting: https://lists.apache.org/thread/toq5pg799ctd7lwdcd6g7zk6xn73h26r Seung-chan On Wed, Jan 12, 2022 at 10:50 PM Seung-chan Ahn wrote: > Hi team, > > Here's the new KIP >

[VOTE] KIP-812: Introduce another form of the `KafkaStreams.close()` API that forces the member to leave the consumer group

Hi team, I feel like we have a finalized proposal for this improvement . I want to know what you think. Thanks in advance for your help, Seung-chan

[jira] [Created] (KAFKA-13667) add a constraints in listeners in combined mode

Luke Chen created KAFKA-13667: - Summary: add a constraints in listeners in combined mode Key: KAFKA-13667 URL: https://issues.apache.org/jira/browse/KAFKA-13667 Project: Kafka Issue Type:

Re: [DISCUSS] Apache Kafka 3.2.0 release

Hi all, I published a release plan for the Apache Kafka 3.2.0 release here: https://cwiki.apache.org/confluence/display/KAFKA/Release+Plan+3.2.0 KIP Freeze: 2 March 2022 Feature Freeze: 16 March 2022 Code Freeze:30 March 2022 At least two weeks of stabilization will follow Code Freeze.