Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

De : Sophie Blee-Goldman Envoyé : mercredi 11 décembre 2024 23:56 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

Envoyé : mercredi 11 décembre 2024 23:56 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you trust the sender and know the content is safe. Few

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

; > De : Matthias J. Sax > Envoyé : vendredi 6 décembre 2024 23:45 > À : dev@kafka.apache.org > Objet : [EXT] Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka > Streams Internal Topics > > Warning External sender Do not click on any lin

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you trust the sender and know the content is safe. One last minor question: You propose to add this new config with

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

that users reset their streams before enabling the configuration. Thanks for your feedback Cheers Sébastien De : Bruno Cadonna Envoyé : mardi 3 décembre 2024 09:14 À : dev@kafka.apache.org Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enf

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

r your feedback > > > > > > Cheers > > Sébastien > > > > > > > > > > > > > > > > De : Bruno Cadonna > > Envoyé : mardi 3 décembre 2024 09:14 > > À : dev@kafka.apache.org > >

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

> > > > > De : Bruno Cadonna > Envoyé : mardi 3 décembre 2024 09:14 > À : dev@kafka.apache.org > Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enforcing > Explicit Naming for Kafka Streams Internal Topics > > Warning Th

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

heers Sébastien De : Bruno Cadonna Envoyé : mardi 3 décembre 2024 09:14 À : dev@kafka.apache.org Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning This might be a fraudulent message! When click

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

De : Bruno Cadonna Envoyé : mardi 26 novembre 2024 19:12 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you trust the sender and know t

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

: jeudi 28 novembre 2024 11:51 À : dev@kafka.apache.org Objet : [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning This might be a fraudulent message! When clicking REPLY, your answers will NOT go to the sender (lbruts...@confl

Recall: RE: [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

sebastien.vi...@michelin.com would like to recall the message, "RE: [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics".

RE: [SUSPICIOUS EXTERNAL MESSAGE] Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning This might be a fraudulent message! When clicking REPLY, your answers will NOT go to the sender (lbruts...@confluent.io.invalid). Instead, replies will be sent to dev@kafka.apache.org. Be cautious! Hi all

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

na > Envoyé : mardi 26 novembre 2024 19:12 > À : dev@kafka.apache.org > Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka > Streams Internal Topics > > Warning External sender Do not click on any links or open any attachments > unless you trust the sender

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

embre 2024 19:12 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you trust the sender and know the content is safe. Hi, Thanks for the KIP!

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

, would it be okay for you if I validate it with you before publishing? cheers ! De : Sophie Blee-Goldman Envoyé : vendredi 22 novembre 2024 01:33 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Inter

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you trust the sender and know the content is safe. First off, thanks for the KIP! I think this is a great idea as it's super ea

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

rom others (e.g., topology optimization and this one) > > I am open to any suggestions. > > > > Is this ticket related to what you are proposing > > https://lists.apache.org/thread/dfgd2vcco7d1omjptfqp92kdocnlf3cq > > > > > > cheers, > > Sébastien > > > &

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

48 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you trust the sender and know the content is safe. Thanks for the KIP. Overall this does sound usef

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

Sébastien De : Matthias J. Sax Envoyé : jeudi 21 novembre 2024 02:48 À : dev@kafka.apache.org Objet : [EXT] Re: [DISCUSS] KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics Warning External sender Do not click on any links or open any attachments unless you

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

Thanks for the KIP. Overall this does sound useful. About Almog's comments (A1) -- I don't think that `topics.internal.require.explicit.naming` would be a good name, as we use `topic.` prefix for actual topic configs. Thus, KS would pickup `internal.require.explicit.naming` and try to apply i

Re: [DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

Hi Sebastien, Thanks for the KIP! In general, I'm a fan of giving users the tools they need to protect their organization so I'm supportive of this proposal. A few nits and comments: A1. [nit] consider 'topics.internal.require.explicit.naming' so that (a) we can group anything else we introduce f

[DISCUSS] KIP-1111: Enforcing Explicit Naming for Kafka Streams Internal Topics

Hi Everyone, I would like to start a discussion on KIP-: Enforcing Explicit Naming for Kafka Streams Internal Topics This proposal aims to add a configuration that preve