[
https://issues.apache.org/jira/browse/KAFKA-7224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17097041#comment-17097041
]
Maatari commented on KAFKA-7224:
--------------------------------
Finally, I don't think providing that would only support my use case, i think
solving this, go in the direction of the statement
{quote}Close the gap between the semantics of KTables in streams and tables in
relational databases. It is common practice to capture changes as they are made
to tables in a RDBMS into Kafka topics (JDBC-connect, Debezium, Maxwell). These
entities typically have multiple one-to-many relationship. Usually RDBMSs offer
good support to resolve this relationship with a join. Streams falls short here
and the workaround (group by - join - lateral view) is not well supported as
well and is not in line with the idea of record based processing.
{quote}
found here
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-213+Support+non-key+joining+in+KTable]
> KIP-328: Add spill-to-disk for Suppression
> ------------------------------------------
>
> Key: KAFKA-7224
> URL: https://issues.apache.org/jira/browse/KAFKA-7224
> Project: Kafka
> Issue Type: Improvement
> Components: streams
> Reporter: John Roesler
> Priority: Major
>
> As described in
> [https://cwiki.apache.org/confluence/display/KAFKA/KIP-328%3A+Ability+to+suppress+updates+for+KTables]
> Following on KAFKA-7223, implement the spill-to-disk buffering strategy.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
