[
https://issues.apache.org/jira/browse/KAFKA-18196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17904953#comment-17904953
]
A. Sophie Blee-Goldman edited comment on KAFKA-18196 at 12/11/24 11:30 PM:
---------------------------------------------------------------------------
My bad – I wasn't aware this config included a stream-stream join optimization
now
I understand why/that we can't enable this by default, and that users can't
turn it on for existing applications, but maybe we should at least log a
warning if a user implements a stream-stream self-join without enabling this
optimization? It seems really easy to miss this (clearly, since I did lol)
was (Author: ableegoldman):
My bad – I wasn't aware of this config!
I understand why/that we can't enable this by default, and that users can't
turn it on for existing applications, but maybe we should at least log a
warning if a user implements a stream-stream self-join without enabling this
optimization? It seems really easy to miss this (clearly, since I did lol)
> Reuse window store for stream-stream self-join
> ----------------------------------------------
>
> Key: KAFKA-18196
> URL: https://issues.apache.org/jira/browse/KAFKA-18196
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: A. Sophie Blee-Goldman
> Assignee: Kuan Po Tseng
> Priority: Major
>
> We can optimize the stream-stream self-join by using only a single copy of
> the state store. Right now this operator gets compiled down into two separate
> window stores for each side, even though both sides are identical.
> See https://github.com/apache/kafka/pull/18111#discussion_r1876844961
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
