Thanks for the KIP Almog.
Overall, I agree that the source-topic optimization for KTables can be
tricky. However, I am not a big fan of changing the configs.
It might be better to disable this optimization in the code on a
per-table basis instead. For this case, one could rewrite the code:
//
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 wrote:
> Thanks for the KIP Almog!
>
> I am in favor of the motivation of this proposal, and just throwing
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:
*
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
