Thanks for the quick feedback, Mathieu. Yes, the first configuration rule whose regex matches will be applied, and no other rules will be used. I've updated the KIP to try to make this more clear, but let me know if it's still not clear.
Best regards, Randall On Tue, May 23, 2017 at 10:07 AM, Mathieu Fenniak < mathieu.fenn...@replicon.com> wrote: > Hi Randall, > > Awesome, very much looking forward to this. > > It isn't 100% clear from the KIP how multiple config-based rules would > be applied; it looks like the first configuration rule whose regex > matches the topic name will be used, and no other rules will be > applied. Is that correct? (I wasn't sure if it might cascade > together multiple matching rules...) > > Looks great, > > Mathieu > > > On Mon, May 22, 2017 at 1:43 PM, Randall Hauch <rha...@gmail.com> wrote: > > Hi, all. > > > > We recently added the ability for Kafka Connect to create *internal* > topics > > using the new AdminClient, but it still would be great if Kafka Connect > > could do this for new topics that result from source connector records. > > I've outlined an approach to do this in "KIP-158 Kafka Connect should > allow > > source connectors to set topic-specific settings for new topics". > > > > *https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 158%3A+Kafka+Connect+should+allow+source+connectors+to+ > set+topic-specific+settings+for+new+topics > > <https://cwiki.apache.org/confluence/display/KAFKA/KIP- > 158%3A+Kafka+Connect+should+allow+source+connectors+to+ > set+topic-specific+settings+for+new+topics>* > > > > Please take a look and provide feedback. Thanks! > > > > Best regards, > > > > Randall >
