Hi Guozhang, Thanks for the KIP! I took a quick look, and I'm really happy to see this underway.
Some quick questions: 1. Can you elaborate on the reason that stores just have a list of serdes, whereas other components have an explicit key/value serde? 1.5. A side-effect of this seems to be that the string-formatted serde description is different, depending on whether the serdes are listed on a store or a topic. Just an observation. 2. You mentioned the key compatibility concern in my mind. We do know that such use cases exist. Namely, our own tests and https://zz85.github.io/kafka-streams-viz/ I'm wondering if we can add a forward-compatible machine-readable format to the KIP, so that even though we must break the parsers right now, maybe we'll never have to break them again. For example, I'm thinking of a "toJson" method on the TopologyDescription that formats the entire topology description as a json string. Thanks again! -John On Fri, Apr 24, 2020, at 00:26, Guozhang Wang wrote: > Hello folks, > > I'd like to start the discussion for KIP-598: > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=148648762 > > It proposes to augment the topology description's sub-classes with store > and source / sink serde information. Let me know what you think, thanks! > > -- > -- Guozhang >
