Hey @wlsc , The upcoming release is 2.1. Here's the release plan: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=91554044
The KIP deadline is 24 Sept., so your kip would need to be voted and accepted by then. The vote itself takes at least 72 hours, per the KIP rules (https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals). This might be a little tight to write your first kip, guide the discussion, and get the vote passed. But I wouldn't stress about it. If you don't get it in for 2.1, there's always 2.2+. I'd recommend to peruse a few recent Streams KIPs (https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Streams) to get a feel for the pattern and just copy one as a template. Let us know if you have any questions! (Just something to think about as you design the KIP): I'm wondering if it would be more ergonomic just to register a ConfiguredInstanceFactory instead of having to subclass StreamsConfig, like this: ```java public interface ConfiguredInstanceFactory { public <T> T getConfiguredInstance(String key, Class<T> type); } ``` and then add a new StreamsConfig constructor for it: ```java new StreamsConfig(Properties config, ConfiguredInstanceFactory configuredInstanceFactory) ``` The main advantages here: * It actually advertises the use case (it otherwise wouldn't be obvious that you can plug in your own DI framework by subclassing StreamsConfig) * you have a much lower risk of accidentally altering the behavior of StreamsConfig in unexpected ways [ Full content available at: https://github.com/apache/kafka/pull/5344 ] This message was relayed via gitbox.apache.org for [email protected]
