Re: Spotting stale KIPs with a better "Under Discussion" table

Hi Tom, Thanks for the nice work! This is very helpful to understand the status of each KIP! And thanks to this tool, it reminds me of a KIP that needs one more vote :) I agree we can automatically change the state of "black" KIPs, and move them into the "Discarded KIPs" or "Dormant/inactive KIPs

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

See

Re: [DISCUSS] KIP-792: Add "generation" field into consumer protocol

Hi David, If you don't have other comments, would you vote for the KIP? Thank you. Luke On Tue, Feb 22, 2022 at 3:13 PM David Jacot wrote: > Thanks, Luke! > > Le mar. 22 févr. 2022 à 08:02, Luke Chen a écrit : > > > Hi David, > > > > Thanks for the comment. > > I've updated the KIP, to add th

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

See

Re: Question about the Log Compaction

Hi, Liang, Currently, we store the MD5 of the record key in OffsetMap. Since it has a large domain (16 bytes), we assume there is no collision there. Thanks, Jun On Wed, Mar 2, 2022 at 1:20 AM 阮良 wrote: > Hi all > > I am confused about the Log Compaction logic，use OffsetMap > to deduplicating

Spotting stale KIPs with a better "Under Discussion" table

Hi All, I am hoping to get more involved in the upstream Kafka community. To that end, I was trying to keep up with the KIPs that were currently under discussion. However, I found it hard to keep track of what was and wasn't being discussed and the progress they were making. Some KIPs appeared

[jira] [Resolved] (KAFKA-13704) Include TopicId in kafka-topics describe output

[ https://issues.apache.org/jira/browse/KAFKA-13704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason Gustafson resolved KAFKA-13704. - Resolution: Duplicate > Include TopicId in kafka-topics describe output > --

[jira] [Created] (KAFKA-13704) Include TopicId in kafka-topics describe output

Jason Gustafson created KAFKA-13704: --- Summary: Include TopicId in kafka-topics describe output Key: KAFKA-13704 URL: https://issues.apache.org/jira/browse/KAFKA-13704 Project: Kafka Issue T

[jira] [Created] (KAFKA-13703) OAUTHBEARER client will not use defined truststore

Adam Long created KAFKA-13703: - Summary: OAUTHBEARER client will not use defined truststore Key: KAFKA-13703 URL: https://issues.apache.org/jira/browse/KAFKA-13703 Project: Kafka Issue Type: Bug

Re: Mirror Maker 2 - High Throughput Identity Mirroring

Hi Ryanne, Is there a PR or code I could take a look at or just the KIP? "shallow mirroring" seems very interesting for our use cases, and I would like to evaluate it internally. Thanks, Antón On Thu, Jul 29, 2021 at 7:02 PM Ryanne Dolan wrote: > Jamie, this would depend on KIP-712 (or simila

Re: Mirror Maker 2 - High Throughput Identity Mirroring

Henry Cai has a PR somewhere. Ryanne On Wed, Mar 2, 2022, 3:36 AM Antón Rodríguez Yuste wrote: > Hi Ryanne, > > Is there a PR or code I could take a look at or just the KIP? "shallow > mirroring" seems very interesting for our use cases, and I would like to > evaluate it internally. > > Thanks,

RE: Kafka Connect - AvroConverter - Unions with Enums Problem

On 2020/05/02 17:22:43 Nagendra Korrapati wrote: > Hello > > Sorry to write this in this mailing list. This is more specific to my problem in using Kafka Connect > > I have Union with Enum in it. ToConnectSchema converted it into Schema.STRUCT type with fields and the enum field as STRING. > > The

[jira] [Resolved] (KAFKA-13658) Upgrade vulnerable dependencies jan 2022

[ https://issues.apache.org/jira/browse/KAFKA-13658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno Cadonna resolved KAFKA-13658. --- Resolution: Fixed > Upgrade vulnerable dependencies jan 2022 > -

Re: [DISCUSS] Apache Kafka 3.2.0 release

Hi Ziming Deng, Thank you for the ping! I added KIP-815 to the release plan! Best, Bruno On 02.03.22 01:14, deng ziming wrote: Hey Bruno, Can we add KIP-815 to the plan? https://cwiki.apache.org/confluence/display/KAFKA/KIP-815%3A++Support+max-timestamp+in+GetOffsetShell

Question about the Log Compaction

Hi all I am confused about the Log Compaction logic，use OffsetMap to deduplicating the log. in my opinion when there is a hash conflict , data may be lost Eg： Record1(key1,offset1) Record2(key2,offset2) Conditionhash(key1) == hash(key2) && (offset1 < offset2)

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

See