Hi Sanghyeok, Thanks a lot for updating the KIP. LGTM, but I would like to ask someone more experienced to take a look at the approach. Also: the client has this this validation for bootstrap.servers: `org.apache.kafka.clients.ClientUtils#parseAndValidateAddresses`, which similar to what the KIP is proposing for application.server, but with a couple extra features on top. Have you seen it? also, as we want to fail fast if application.server is invalid, should we fail fast for bootstrap.servers? Sorry for asking one question at a time, I am learning on the go.
On Tue, Dec 9, 2025 at 5:08 AM 안상혁 <[email protected]> wrote: > > Hi Nikita, > > Thanks again for pointing me to KIP-1161. > > I have updated the KIP as we discussed: > - Removed the two phase rollout with a warning first and an error later > - Added a ConfigDef.Validator for application.server in StreamsConfig > - Clarified that the validator reuses the existing HostInfo endpoint parsing > logic and only moves the existing failure earlier to configuration time > > Since applications with an invalid application.server value already fail > today when HostInfo parses the endpoint, > this change should not affect any correctly working applications, but it > makes the error surface earlier and more explicit. > > When you have time, I would appreciate it if you could take another look and > let me know whether the updated text matches your expectations. > > Best regards, > Sanghyeok An
