Take a look at the DefaultConfigPropertyFilter class, which supports customizable blacklists via config.properties.blacklist.
Ryanne On Tue, Jan 14, 2020, 6:05 AM Vishal Santoshi <vishal.santo...@gmail.com> wrote: > Thank you for the prompt reply, Very much appreciated. I am not sure > disable config sync is an option for us. How do I blacklist retention.ms > ? > > On Tue, Jan 14, 2020 at 12:47 AM Ryanne Dolan <ryannedo...@gmail.com> > wrote: > > > Vishal, there is no support for overriding topic configuration like > > retention. Instead, remote topics will have the same configuration as > their > > source topics. You could disable config sync or blacklist retention.ms > to > > prevent that from happening, and then alter retention for remote topics > > manually if you need to. > > > > KIP-158 might help with this in the future by allowing you to control how > > Connect creates topics, to some extent. > > > > Ryanne > > > > On Mon, Jan 13, 2020, 9:55 PM Vishal Santoshi <vishal.santo...@gmail.com > > > > wrote: > > > > > Can I override the retention on target topics through mm2.properties ? > > It > > > should be as simple as stating the retention.ms globally ? Am also > > > curious whether it can more at a single channel level ? > > > > > > For example A->B, topic on B should have a retention of x and for B->A > > the > > > retention is y.. > > > > > > Is that possible? > > > > > > Thanks. > > > > > >
