Hi Ismael, If I understand your question, in KIP-392 the `client.rack` config serves both as setting the rack and as the on/off switch for the whole feature. In KIP-1123, these are separate. Originally I thought that having separate configs would be more explicit and more future-proof: in case some other new feature that rely on the `client.rack` setting is added. Do you think I should change it to the single config to be uniform with KIP-392?
Best, Ivan On Sun, Jul 20, 2025, at 23:15, Ismael Juma wrote: > Hi, > > Thanks for the KIP. One question I have is why two configs are needed > instead of a single config? KIP-392 specifies a single client side config. > It would be good to be consistent across the clients. > > Ismael > > On Fri, Dec 20, 2024 at 3:37 AM Ivan Yurchenko <i...@ivanyu.me> wrote: > > > Hello all, > > > > I'd like to propose a new KIP to discuss: KIP-1123: Rack-aware > > partitioning for Kafka Producer [1]. > > > > Best, > > Ivan Yurchenko > > > > [1] > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-1123%3A+Rack-aware+partitioning+for+Kafka+Producer > > >
