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

See

[jira] [Resolved] (KAFKA-13752) Using `equals` instead of `==` when Uuid compare in Java

[ https://issues.apache.org/jira/browse/KAFKA-13752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jacot resolved KAFKA-13752. - Fix Version/s: 3.2.0 3.1.1 3.3.0 Resolution: Fixed

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

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.1 #91

See

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

Hi Hao, Thank you for the KIP! Regarding option 1, I would not use `Emitted.onWindowClose()` since that does not seem compatible with the proposed flow. Conceptually, now the flow states that the aggregation is triggered on window close and all aggregation results are emitted. `Emitted` sugge

Build failed in Jenkins: Kafka » Kafka Branch Builder » 3.2 #2

See Changes: -- [...truncated 523677 lines...] [2022-03-22T11:14:53.094Z] > Task :connect:api:copyDependantLibs UP-TO-DATE [2022-03-22T11:14:53.094Z] > Task :connect:api:jar UP-

Re: [VOTE} KIP-796: Interactive Query v2

Hi John, The already implemented query types work as expected, don't they? I do not know the specific concerns, but it seems that this is the situation that motivated you to mark the APIs as @Evolving. Keeping the IQv2 API in 3.2 does not contradict the accepted KIP, right? In case, we decid

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

See

[jira] [Created] (KAFKA-13757) Improve the annotations of all related methods of DelegationToken in the Admin class

RivenSun created KAFKA-13757: Summary: Improve the annotations of all related methods of DelegationToken in the Admin class Key: KAFKA-13757 URL: https://issues.apache.org/jira/browse/KAFKA-13757 Project:

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.1 #92

See

Jenkins build is unstable: Kafka » Kafka Branch Builder » 3.2 #3

See

Re: [VOTE} KIP-796: Interactive Query v2

Thanks Bruno, Yes, although IQv2 is not fully implemented (it doesn't query global stores, and it doesn't support every query we ultimately want), the queries that are implemnted do work as expected. The main concern was that, right now, it's the job of the Metered layer to translate queries and

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

See

Re: [VOTE} KIP-796: Interactive Query v2

Hi John, Originally I was leaning towards making IQv2 APIs more or less stable while being released for the first time, but after some second thoughts I'm now feeling it's okay to take it in a more evolving manner. So I'm preferring to keep it and be open for breaking changes in the future. Guoz

Re: [VOTE] KIP-761: Add Total Blocked Time Metric to Streams

Hello, I discovered a bug in the design of this metric. The bug is documented here: https://github.com/apache/kafka/pull/11805. We need to include time the producer spends waiting on topic metadata into the total blocked time. But to do this we would need to add a new producer metric that tracks t

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

Hi Bruno, Could you elaborate a bit more here, what's the semantic difference between "the aggregation is triggered on window close and all aggregation results are emitted." for trigger(TriggerParameters.onWindowClose()), and "the aggregation is configured to only emit final results." for trigger(

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

Hi Guozhang, There is no semantic difference. It is a cosmetic difference. Conceptually, I relate `Emitted` with the aggregation and not with `trigger()` in the API flow, because the aggregation emits the result not `trigger()`. Therefore, I proposed to not use `Emitted` as the name of the co

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.1 #93

See

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

Hi Bruno, Guozhang, I think `Emitted.onWindowClose` is inspired by `Suppressed.untilWindowClose`. Given `Suppressed.untilWindowClose` is used inside `suppress()`, `Suppressed` sounds good. However, `trigger()` is a builder style setting instead of an action, `Emitted` may be a bit off. How about

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

I see what you mean now, and I think it's a fair point that composing `trigger` and `emitted` seems awkward. Re: data process operator v.s. control operator, I shared your concern as well, and here's my train of thoughts: Having only data process operators was my primary motivation for how we add

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

`windowedStream.onWindowClose()` was the original option 1 (`windowedStream.emitFinal()`) but was rejected because we could add more emit types and this will result in adding more functions. I still prefer the "windowedStream.someFunc(Controlled.onWindowClose)" model since it's flexible and clear t

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.1 #94

See

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

Hi, Artem, Thanks for the KIP. +1 from me. Jun On Mon, Mar 21, 2022 at 4:52 PM Artem Livshits wrote: > Hi all, > > I'd like to start a vote on > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-794%3A+Strictly+Uniform+Sticky+Partitioner > . > > -Artem >

Re: [DISCUSS] KIP-651 - Support PEM format for SSL certificates and

Hi Dejan and Rajini I tend to agree with both the arguments when I read them in isolation :) However, what I feel is - we have to also take an operator's view of this setup. If we have encrypted keys/certs already it may be easier to fit with file based material but if we don't have material encry

Re: [DISCUSS] KIP-651 - Support PEM format for SSL certificates and

just a clarification on the part "... we are not left with any choice but to use the file based config .." - That is "if" we want material rotations to be picked up automatically. On Tue, Mar 22, 2022 at 1:57 PM Maulin Vasavada wrote: > Hi Dejan and Rajini > > I tend to agree with both the argum

Re: [DISCUSS] KIP-825: introduce a new API to control when aggregated results are produced

Thanks for the great summary Hao. I'm still learning towards option 2) here, and I'm in favor of `trigger` as function name, and `Triggered` as config class name (mainly to be aligned with other config class names). Also want to see other's preferences between the options, as well as the namings.

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

Hello Seung-chan, Just checking if you are still working to complete this KIP? Since we have just passed the freeze deadline of 3.2, the KIP would only be completed in 3.3.0. On Sat, Feb 19, 2022 at 5:37 AM Seung-chan Ahn wrote: > This vote passes with: > - 3 +1 (binding) votes from Guozhang, J

[jira] [Created] (KAFKA-13758) Exclusive locking in kafka.coordinator.group.GroupMetadata.inLock(GroupMetadata.scala:227

Sree Vaddi created KAFKA-13758: -- Summary: Exclusive locking in kafka.coordinator.group.GroupMetadata.inLock(GroupMetadata.scala:227 Key: KAFKA-13758 URL: https://issues.apache.org/jira/browse/KAFKA-13758

[jira] [Created] (KAFKA-13759) Disable producer idempotency by default in producers instantiated by Connect

Konstantine Karantasis created KAFKA-13759: -- Summary: Disable producer idempotency by default in producers instantiated by Connect Key: KAFKA-13759 URL: https://issues.apache.org/jira/browse/KAFKA-13759

Re: [VOTE} KIP-796: Interactive Query v2

The old API IQv1 is not deprecated yet, so I don't see a reason to revert. We might not want to "advertise" the IQv2 in the release announcement though if it's not complete and unstable right now. We might also not want to mention it in the docs? Not sure if there was already docs PR. If yes,

Re: [VOTE} KIP-796: Interactive Query v2

Thanks, all. This all sounds good to me. I’ll send a PR to add a warning/disclaimer to the javadoc. I don’t believe we updated the docs yet, but I will double-check. Thanks, John On Tue, Mar 22, 2022, at 20:06, Matthias J. Sax wrote: > The old API IQv1 is not deprecated yet, so I don't see a

Jenkins build is still unstable: Kafka » Kafka Branch Builder » 3.2 #4

See

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

See

[jira] [Created] (KAFKA-13760) Kafka 2.8.1 : log clean skip __consumer__offsets-45

zhangzhisheng created KAFKA-13760: - Summary: Kafka 2.8.1 : log clean skip __consumer__offsets-45 Key: KAFKA-13760 URL: https://issues.apache.org/jira/browse/KAFKA-13760 Project: Kafka Issue T

[jira] [Created] (KAFKA-13761) KafkaLog4jAppender deadlocks when idempotence is enabled

Yang Yu created KAFKA-13761: --- Summary: KafkaLog4jAppender deadlocks when idempotence is enabled Key: KAFKA-13761 URL: https://issues.apache.org/jira/browse/KAFKA-13761 Project: Kafka Issue Type: Bu

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

See