Re: [DISCUSS] KIP-592: MirrorMaker should replicate topics from earliest

Same. There is a backward compatibility risk (we are changing the behavior, and the assessment that it won't affect anyone may be correct - but there is a risk that people depend on existing behaviors in ways we didn't consider) Remember that users are yelling on twitter even when we do small

Re: [DISCUSS] KIP-602 - Change default value for client.dns.lookup

Hi Badai, I think this is a good change. Can you please address the issues raised by KIP-235? That was the reason why we did not do it previously. Ismael On Mon, Apr 27, 2020 at 5:46 PM Badai Aqrandista wrote: > Hi everyone > > I have opened this KIP to have client.dns.lookup default value

Re: [DISCUSS] KIP-317 - Add end-to-end data encryption functionality to Apache Kafka

Hi Sonke Thanks for bringing this for discussion. There are lot of considerations even if we assume we have end-to-end encryption done. Example depending upon company's setup there could be restrictions on how/which encryption keys are shared. Environment could have multiple security and network

Re: [DISCUSS] KIP-317 - Add end-to-end data encryption functionality to Apache Kafka

Adam, I agree, seems reasonable to limit the broker's responsibility to encrypting only data at rest. I guess whole segment files could be encrypted with the same key, and rotating keys would just involve re-encrypting entire segments. Maybe a key rotation would involve closing all affected

Re: [DISCUSS] KIP-317 - Add end-to-end data encryption functionality to Apache Kafka

Hi All I typed up a number of replies which I have below, but I have one major overriding question: Is there a reason we aren't implementing encryption-at-rest almost exactly the same way that most relational databases do? ie: https://wiki.postgresql.org/wiki/Transparent_Data_Encryption I ask

[jira] [Created] (KAFKA-9976) Aggregates should reuse repartition nodes

Bill Bejeck created KAFKA-9976: -- Summary: Aggregates should reuse repartition nodes Key: KAFKA-9976 URL: https://issues.apache.org/jira/browse/KAFKA-9976 Project: Kafka Issue Type: Improvement

Re: [DISCUSS] KIP-606: Add Metadata Context to MetricsReporter

Thanks, Xavier. Looks great. On Fri, May 8, 2020 at 7:31 PM Xavier Léauté wrote: > > This does seem very useful. A minor request would be to mention the new > > configs for Connect, Streams and clients, specifically that because they > > are optional they will not hinder upgrades, and because

Build failed in Jenkins: kafka-trunk-jdk11 #1438

See Changes: [github] MINOR: Improve formatting in docs (#8611) -- [...truncated 4.76 MB...] at kafka.log.LogCleaner.$anonfun$startup$2(LogCleaner.scala:146)

Re: [DISCUSS] KIP-317 - Add end-to-end data encryption functionality to Apache Kafka

Tbh tom is right it is entirely possible to support end 2 end encryption today without broker or client changes with serializers. Infact i know many companies doing this.As such maybe a good approach would be to provide a default encryption and decryption serde thats able to be used rather than