I like that API! I'll wait a day or two to give people the opportunity to chime in and then update the wiki.
Thanks for the feedback, Almog On Mon, Jan 18, 2021 at 10:00 PM Guozhang Wang <wangg...@gmail.com> wrote: > Thanks for the KIP Almog! > > I am in favor of the motivation of this proposal, and just throwing out an > alternative about the API here: what do you think if we reuse the > `TOPOLOGY_OPTIMIZATION` config but allow it it accept a list of strings > instead of a single string, in the following semantics: > > * "none": disable all optimization rules. > * "all", "-rule1", "-rule2": enable all optimization except rule1 and > rule2. > * "rule1", "rule2": enable only rule1 and rule2 (i.e. enumerate). > * "none", "rule1", "rule2": not accepted, throw error. > > -------- > > Of course, for this KIP's scope itself, we can just do it for one specific > rule of "source-changelog". I'm just wondering about the general framework > for extending the current configuration here. > > Guozhang > > > On Wed, Jan 13, 2021 at 10:42 AM Almog Gavra <al...@confluent.io> wrote: > > > Hello, > > > > I would like to start the discussion thread for KIP-705: > > > > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-705%3A+Selectively+Disable+Topology+Optimizations > > > > The KIP is proposing an additional streams configuration that allows to > > selectively disable optimizations under the topology.optimization bucket. > > Specifically, the first optimization that can be disabled is the > > source-topic-as-changelog optimization. > > > > Cheers, > > Almog > > > > > -- > -- Guozhang >
