Re: [DISCUSS] Apache Kafka 3.2.0 release

Hi Haruki, Thank you for proposing to add KIP-764! I added the KIP to the release plan. Best, Bruno On 17.02.22 00:32, Haruki Okada wrote: Hi Bruno, Thank you for driving the release ! Can we add KIP-764 to the plan? ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-764%3A+Configurable

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

See

[jira] [Created] (KAFKA-13674) Failure on ZOS due to IOException when attempting to fsync the parent directory

Hong Yi Zhang created KAFKA-13674: - Summary: Failure on ZOS due to IOException when attempting to fsync the parent directory Key: KAFKA-13674 URL: https://issues.apache.org/jira/browse/KAFKA-13674 Pro

Re: [DISCUSS] KIP-813 Shared State Stores

> 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 find > and hard to read. > >

Re: [DISCUSSION] New broker metric. Per partition consumer offset

Hello, just a minor fllow-up > Client is already collecting consumer-fetch-manager-metrics metrics, can > report them to cluster, the broker can feed metrics to subscriptions, and > this "just works" without new code in group coordinator. This approach looks very questionable for me. Group lea

Kafka Mailing List ?

Hi! Just reading "Kafka:the definitive Guide", and saw that there is a mailing list Can I sign up for this please? Thx Grüße, /Jeremy Magenta Telekom Jeremy AMER SQA Appication System Manager Tel: +43 676 8200 6155 E-Mail: jeremy.a...@magenta.at T-Mobile Austria

Re: Kafka Mailing List ?

Hi Jeremy Different types of mailing lists associated with Kafka are listed here: https://kafka.apache.org/contact The page also tells you how to subscribe to a mailing list (it is as simple as sending an email to a particular email address). In addition to mailing lists, Apache also maintains a

Re: [DISCUSS] KIP-813 Shared State Stores

Hi Daan, I think for the read-only state stores you'd need ot slightly augment the checkpointing logic so that it would still write the checkpointed offsets while restoring from the changelogs. Guozhang On Thu, Feb 17, 2022 at 7:02 AM Daan Gertis wrote: > > Could you add more details about th

Call for review: KIP-618

Hi all, It's been a little over eight months since KIP-618 ( https://cwiki.apache.org/confluence/display/KAFKA/KIP-618%3A+Exactly-Once+Support+for+Source+Connectors) was approved, and nearly as long since a feature- and test-complete implementation (initially published in https://github.com/apache

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

Regarding the last question Matthias had, I wonder if it's similar to my first email's point 2) above? I think the rationale is that, since reference checks are relatively very cheap, it is worthwhile to pay this extra runtime checks and in return to have a single consolidated ProcessorSupplier pro

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

Thanks Jorge, overall looks good to me. Maybe we can clarify a bit in the wiki that the reason we have to not include the additional `final String... stateStoreNames` params in the new `process` API is that we need to have overloaded functions which takes `ProcessorSupplier<...> ` where the output

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

Thanks Sueng-chan, I'm +1 on the proposal. Guozhang On Tue, Feb 15, 2022 at 7:06 AM Seung-chan Ahn wrote: > Hi team, > > I feel like we have a finalized proposal for this improvement > . > I want to know what you think. > > Thanks in advance for y

[jira] [Created] (KAFKA-13675) Null pointer exception with kafka streams application reset tool with --to-datetime

Paul Callahan created KAFKA-13675: - Summary: Null pointer exception with kafka streams application reset tool with --to-datetime Key: KAFKA-13675 URL: https://issues.apache.org/jira/browse/KAFKA-13675

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

Hi, Artem, Thanks for the KIP. A few comments below. 1. I agree with Luke that having the partitioner returning -1 is kind of weird. Could we just change the implementation of DefaultPartitioner to the new behavior? 2. partitioner.sticky.batch.size: Similar question to Luke. I am not sure why we

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

Thanks for the KIP, Sueng-Chan! I’m +1 (binding) -John On Thu, Feb 17, 2022, at 12:58, Guozhang Wang wrote: > Thanks Sueng-chan, > > I'm +1 on the proposal. > > > Guozhang > > On Tue, Feb 15, 2022 at 7:06 AM Seung-chan Ahn > wrote: > >> Hi team, >> >> I feel like we have a finalized proposal fo

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

It probably deserves its own thread to start discussing ideas. Yes. My question was: if we think it's time to do a DSL 2.0, should we drop this KIP and just fix via DSL 2.0 instead? You're right. I'm not proposing the method signature. What signature do you propose? I don't see an update

Re: [DISCUSS] KIP-813 Shared State Stores

Thanks for updating the KIP! I am wondering if we would need two overloads of `addReadOnlyStateStore` one w/ and one w/o `TimestampExtractor` argument to effectively make it an "optional" parameter? Also wondering if we need to pass in a `String sourceName` and `String processorName` paramet

Re: Call for review: KIP-618

Hi Chris, Thanks for all the PRs (wow, 10K lines of changes). EOS on source connector is a great feature in Kafka connect! I will start to review this PR next week: Producer fencing API for admin client: https://github.com/apache/kafka/pull/11777 Thank you. Luke On Fri, Feb 18, 2022 at 2:36 AM

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

Hi Seung-chan, Thanks for the KIP! I like the optimization to have a close method to force leave group. Some minor comments: 1. in the "public interfaces", there are many `close` method listed, but I believe you only want to introduce the one with `CloseOptions`, right? Could you add some comment

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

On Fri, 18 Feb 2022 at 02:16, Matthias J. Sax wrote: > > It probably deserves its own thread to start discussing ideas. > > Yes. My question was: if we think it's time to do a DSL 2.0, should we > drop this KIP and just fix via DSL 2.0 instead? > > Good question. Would love to hear what others th